VulnerabilityPublished 22 Aug 2024Updated 9 Nov 2026

CVE-2024-43785: gitoxide-core does not neutralize special characters for terminals

Affects gitoxide-coreSource GCVE Database

Compare

Not known to be exploited · CVSS 2.5 Low.

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.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 22 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

Affected software

Product	Affected	Fixed in
crates.iogitoxide-core`pkg:cargo/gitoxide-core`Other threats	Affected >=0.0.0-0	Fixed in–

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

AI-suggested

Users should be aware that cloning or operating on untrusted repositories with gitoxide-core may produce misleading terminal output. Avoid running gitoxide-core commands on untrusted repositories or in environments where terminal output manipulation could cause confusion. Since this vulnerability affects only terminal output and not underlying data integrity, no urgent remediation is required. Monitor vendor advisories for any future patches or updates addressing this issue.

Description

gitoxide-core's gix and ein commands output repository metadata, including pathnames, author names, and commit messages, directly to terminals without neutralizing special characters such as ANSI escape sequences. This allows a malicious repository to produce misleading or manipulated terminal output, including colored text and cursor repositioning, which can conceal files or mimic error messages. The impact is mostly an annoyance and limited to Unix-like systems with ANSI-capable terminals. Windows systems are less affected due to filename and terminal limitations. The vulnerability does not affect other applications unless they use gitoxide-core, which is discouraged. No known exploits are reported, and the CVSS score is low.

Impact

The vulnerability allows an attacker controlling a repository to cause terminal output from gitoxide-core commands to display misleading or manipulated messages by embedding special characters and ANSI escape sequences in repository metadata. This can conceal files or fabricate error messages in terminal output, potentially confusing users. However, the impact is limited to terminal display and does not affect file system integrity or other applications. Windows systems are less affected due to filename and terminal constraints. There are no reports of exploitation in the wild, and the overall impact is considered low severity.

Summary

The gitoxide-core library, underlying the gix and ein commands, fails to sanitize special characters including newlines, backspaces, and ANSI escape sequences in repository metadata such as paths, author/committer names, and commit messages. When this metadata is output to terminals, it can alter terminal behavior by changing colors, repositioning the cursor, clearing the screen, or modifying the terminal title bar. This can be exploited by an attacker controlling a repository to misrepresent repository contents or fabricate error messages in terminal output. The effect is limited to terminal output and does not affect redirected output or other applications not using gitoxide-core. The vulnerability primarily affects Unix-like systems; Windows terminals are less susceptible due to character and terminal support differences. The exploit requires the attacker to predict how repository data is displayed, limiting the scope of convincing attacks.

References

Community reviews

Loading reviews…