VulnerabilityPublished 6 Sep 2024Updated 9 Nov 2026

CVE-2024-45405: gix-path improperly resolves configuration path reported by Git

Affects gix-pathSource GCVE Database

Compare

Not known to be exploited · CVSS 6.0 Medium : upgrade to 0.10.11 when convenient.

Data as of 9 Nov 2026, 11:23 UTC

CVSS 3.1 base score

6.0Medium

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

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

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

Attack Vector: Local
Attack Complexity: High
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 6 Sep 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.11.

Affected software

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

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

AI-suggested

A patch is available in gix-path version 0.10.11 that correctly handles Git configuration paths by using the '-z'/'--null' option to obtain literal paths and avoid misinterpretation. Users and administrators should upgrade to version 0.10.11 or later to remediate this vulnerability. No additional mitigation steps are required once the patch is applied.

Description

The gix-path library improperly resolves configuration file paths reported by Git when those paths contain unusual or non-ASCII characters. This flaw arises because gix-path does not use Git's null-terminated output option and attempts to parse quoted paths by stripping quotation marks without reversing encoding transformations. As a result, an attacker with limited local user access can craft malicious configuration files that gix-path mistakenly loads, potentially leading to code execution. The vulnerability affects versions before 0.10.11 and has a CVSS score of 6.0. A fix is available in version 0.10.11.

Impact

An attacker with limited local user privileges can exploit this vulnerability to inject malicious Git configuration files that gix-path incorrectly resolves and loads. This can lead to arbitrary code execution when gix-path processes these configurations. The CVSS score of 6.0 reflects a medium severity with high confidentiality and integrity impact but requires local access and user interaction.

Summary

gix-path runs Git commands to locate configuration files associated with the Git installation. It calls 'git config -l --show-origin' but does not use the '-z'/'--null' option to get literal paths. Instead, it tries to parse quoted paths by removing quotation marks. However, when Git outputs quoted paths, it may encode non-ASCII characters (e.g., 'é' becomes '\303\251'), which gix-path does not correctly decode. This can cause gix-path to open attacker-controlled configuration files that appear valid due to this misinterpretation. An attacker with a limited user account can exploit this by creating specially named configuration files to inject configuration directives, potentially leading to code execution. The issue is fixed in gix-path version 0.10.11.

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