GitApplication
CVE-2024-52005
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGit 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 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceANSI escape sequence injection vulnerability in Git's sideband channel used for transporting remote informational/error messages during clone, fetch, or push operations. The messages are printed to stderr with a 'remote:' prefix without sanitizing malicious ANSI escape sequences that can hide information, misrepresent content, or trick users into executing untrusted scripts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitApplication
<= 2.40.4>= 2.41.0, <= 2.41.3>= 2.42.0, <= 2.42.4>= 2.43.0, <= 2.43.6>= 2.44.0, <= 2.44.3>= 2.45.0, <= 2.45.3>= 2.46.0, <= 2.46.3>= 2.47.0, <= 2.47.1>= 2.48.0, <= 2.48.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Git versionRun `git --version` to determine the installed versionAffected if The version is <= 2.40.4; >= 2.41.0 and <= 2.41.3; >= 2.42.0 and <= 2.42.4; >= 2.43.0 and <= 2.43.6; >= 2.44.0 and <= 2.44.3; >= 2.45.0 and <= 2.45.3; >= 2.46.0 and <= 2.46.3; >= 2.47.0 and <= 2.47.1; >= 2.48.0 and <= 2.48.1
-
Identify use of clone/fetch/push operationsReview recent Git activity for any clone, fetch, or push operations, especially with remotes that may be untrustedAffected if You have performed clone, fetch, or push operations using a vulnerable Git version from any remote repository
-
Inspect stderr output for remote messagesDuring Git operations, examine stderr output for messages prefixed with 'remote:' - this indicates the sideband channel is in useAffected if Stderr shows 'remote:' prefixed messages during network operations, confirming the vulnerable code path is being exercised
You are affected if your installed Git version falls within any of the vulnerable ranges listed and you perform clone, fetch, or push operations that produce remote messages on stderr.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Git to the latest patched version. Avoid recursive clone/fetch/push operations from untrusted remote repositories until systems are patched.
Git 2.44.0 or later (or 2.40.5+, 2.41.4+, 2.42.5+, 2.43.7+ for respective release branches)
- Check current Git version by running: git --version
- Upgrade to the latest stable Git version for your platform: On macOS: brew install git; On Linux: sudo apt-get update && sudo apt-get install git (or use your package manager); On Windows: Download latest installer from git-scm.com
- Verify the upgrade was successful by running: git --version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Git
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-52005 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data