CVE-2024-52006
Git ≤ 2.40.4
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/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-52006 is a low-severity Improper Encoding or Escaping of Output (CWE-116) vulnerability in Git Git. Its CVSS base score is 2.1 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 39% of CVEs by exploit likelihood; 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-52006 affects Git, a distributed revision control system, specifically its line-based protocol used to exchange information between Git and credential helpers. Certain ecosystems, most notably .NET and node.js, interpret single Carriage Return (CR) characters as newlines, rendering the existing protections against CVE-2020-5260 incomplete for credential helpers that process CRs in this way. The vulnerability is associated with CWE-116 (Improper Encoding or Escaping of Output), CWE-147 (Less Robust Fix), and CWE-150 (Improper Neutralization of CRLF Sequences), and impacts Git versions prior to the patched releases.
The vulnerability carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), allowing remote, unauthenticated attackers with low complexity and no user interaction to achieve high-impact confidentiality violations. Exploitation occurs when users clone repositories from untrusted sources, where attackers can manipulate protocol responses using CR characters to bypass safeguards, potentially leading to unauthorized access to stored credentials via affected credential helpers.
Git has addressed the issue in commit b01b9b81d36759cdcd07305e78765199e1bc2060, which is included in release versions v2.48.1, v2.47.2, v2.46.3, v2.45.3, v2.44.3, v2.43.6, v2.42.4, v2.41.3, and v2.40.4. Security practitioners should advise users to upgrade immediately. For those unable to upgrade, mitigation involves avoiding clones from untrusted URLs, particularly recursive clones. Detailed advisories are available from Git's GitHub security pages (GHSA-qm7j-c969-7j4q, GHSA-r5ph-xg7q-xfrp, and Git Credential Manager's GHSA-86c2-4x57-wc8g) and Debian LTS announcements.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-46253
Vulnerability Data
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. Git defines a line-based protocol that is used to exchange information between Git and Git…
more
credential helpers. Some ecosystems (most notably, .NET and node.js) interpret single Carriage Return characters as newlines, which renders the protections against CVE-2020-5260 incomplete for credential helpers that treat Carriage Returns in this way. This issue has been addressed in commit `b01b9b8` which is included in release versions v2.48.1, v2.47.2, v2.46.3, v2.45.3, v2.44.3, v2.43.6, v2.42.4, v2.41.3, and v2.40.4. Users are advised to upgrade. Users unable to upgrade should avoid cloning from untrusted URLs, especially recursive clones.
- 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
Input validation enforces neutralization of terminator characters before data reaches 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.