CVE-2024-52005
Git ≤ 2.40.4
Raw vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2024-52005 is a high-severity Improper Encoding or Escaping of Output (CWE-116) vulnerability in Git Git. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-52005 is a vulnerability in Git, a widely used source code management tool, stemming from improper handling of informational and error messages transmitted via the sideband channel during operations like cloning, fetching, or pushing from a remote server. These messages, prefixed with "remote:", are printed directly to the client's standard error output, which is typically connected to a terminal supporting ANSI escape sequences. Git previously lacked protections against these sequences, allowing malicious control sequences to be embedded in the messages.
The vulnerability can be exploited by an attacker controlling a remote Git server or repository. A victim running Git commands against this malicious remote would receive crafted "remote:" messages on their terminal, enabling the attacker to hide or misrepresent information or trick the user into executing untrusted scripts. Exploitation requires user interaction (UI:R), occurs over the network with low complexity and no privileges (AV:N/AC:L/PR:N), and results in high confidentiality, integrity, and availability impacts (C:H/I:H/A:H), as scored at CVSS 3.1 8.8. It is associated with CWE-116 (Improper Encoding or Escaping of Output) and CWE-150 (Improper Neutralization of Escape, Meta, or Control Sequences).
The Git security advisory (GHSA-7jjc-gg6m-3329) and related public mailing list discussions note that patches are under review on the git-security mailing list as requested for transparency. Users should update Git as soon as patches are available. Those unable to upgrade are advised to avoid recursive clones unless from trusted sources.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-46250
Vulnerability Data
Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed…
more
with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.2V1.2.1V1.2.3V1.2.10
Mitigating Controls (NIST 800-53 r5) AI
SI-10 requires validation/sanitization of inputs that directly stops escape/meta/control sequences from reaching downstream components.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper output encoding to prevent injection and message malformation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards explicitly require correct output encoding and escaping to preserve message structure.
Security testing can detect missing or incorrect encoding but does not itself implement the control.
Secure development life cycle mandates output encoding/escaping practices that directly prevent improper encoding.
Application security requirements include explicit rules for safe output handling and encoding.
Secure architecture principles reduce the likelihood of missing encoding but do not prescribe the actual technique.