Skip to content

In Quarkus, git credentials could be inadvertently published

Low severity GitHub Reviewed Published Mar 13, 2024 to the GitHub Advisory Database • Updated Apr 3, 2024

Package

maven io.quarkus:quarkus-kubernetes-deployment (Maven)

Affected versions

< 3.7.3

Patched versions

3.7.3

Description

A vulnerability was found in Quarkus. In certain conditions related to the CI process, git credentials could be inadvertently published, which could put the git repository at risk.

References

Published by the National Vulnerability Database Mar 13, 2024
Published to the GitHub Advisory Database Mar 13, 2024
Reviewed Mar 13, 2024
Last updated Apr 3, 2024

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N

EPSS score

0.045%
(17th percentile)

Weaknesses

CVE ID

CVE-2024-1979

GHSA ID

GHSA-7g97-7r3c-5cc6

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.