VulnerabilityPublished 31 Aug 2024Updated 9 Nov 2026

CVE-2024-45305: gix-path uses local config across repos when it is the highest scope

Affects gix-pathSource GCVE Database

Compare

Not known to be exploited · CVSS 2.5 Low : upgrade to 0.10.10 when convenient.

Data as of 9 Nov 2026, 11:23 UTC

CVSS 3.1 base score

2.5Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.10.10

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gix-path to 0.10.10.

Affected software

Product	Affected	Fixed in
crates.iogix-path`pkg:cargo/gix-path`Other threats	Affected >=0.0.0-0 <0.10.10	Fixed in 0.10.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in gix-path version 0.10.10. Users and maintainers should upgrade to this version to resolve the issue. There are no vendor advisories indicating that no action is required or that the issue is already mitigated otherwise.

Description

The gix-path library incorrectly treats local Git repository configuration as system-wide configuration under certain conditions, leading to potential leakage of sensitive information such as credentials between repositories. This occurs when higher scoped configuration files are missing or deliberately disabled, causing local configuration to be misinterpreted as installation-level configuration. This can result in credentials intended for one repository being sent to another during operations like cloning. The issue is fixed in version 0.10.10.

Impact

The vulnerability can lead to unintended exposure of sensitive information, such as authentication credentials, from one Git repository to another. This may cause credentials meant for a trusted repository to be sent to a less trusted repository, potentially compromising security. The impact is limited by the requirement for specific environment configurations and user actions, and the CVSS score is low (2.5).

Summary

gix-path executes git commands to determine the path of the highest scoped Git configuration file but mistakenly treats local repository configuration as system-wide if no higher scoped configuration is found. This can happen when system or global configuration files are absent or disabled via environment variables (e.g., GIT_CONFIG_SYSTEM=/dev/null, GIT_CONFIG_NOSYSTEM=1). Consequently, sensitive data such as credentials configured locally for one repository may be exposed or sent to another repository during operations like cloning. The vulnerability is addressed in gix-path version 0.10.10.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Nov 2026, 11:23 UTC

Technical details

References

Community reviews

Related threats