GitApplication · Git Scm
CVE-2024-32021
A fix is available.
Upgrade to 2.39.4 / 2.40.2 or later.
See remediation →
74/100
Remediation priority · Elevated
Public exploit
No privileges
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 revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the `objects/` directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary user-owned files on the same filesystem in the target Git repository's `objects/` directory. When cloning a repository over the filesystem (without explicitly specifying the `file://` protocol or `--no-local`), the optimizations for local cloning will be used, which include attempting to hard link the object files instead of copying them. While the code includes checks against symbolic links in the source repository, which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check, and then a symlink during the operation, this will allow the adversary to bypass the check and create hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.
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 analysisA detailed technical summary for this CVE is being prepared.
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
Affected:
< 2.39.4>= 2.40.0, < 2.40.2>= 2.42.0, < 2.42.2>= 2.43.0, < 2.43.4= 2.41.0= 2.44.0= 2.45.0
FedoraOperating system
Affected:
= 40
Debian LinuxOperating system
Affected:
= 10.0= 11.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
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 · scoped
Upgrade available
Upgrade to 2.39.4 / 2.40.2 / 2.42.2 or later
Fixed in
2.39.42.40.22.42.2
Recommended fix
High confidence
Upgrade to Git 2.39.4, 2.40.2, 2.41.1, 2.42.2, 2.43.4, 2.44.1, or 2.45.1 (depending on your current branch)
- 1. Check your current Git version by running: git --version
- 2. Based on your current version, upgrade to the appropriate fixed release: For 2.39.x branches, upgrade to 2.39.4; For 2.40.x, upgrade to 2.40.2; For 2.41.x, upgrade to 2.41.1; For 2.42.x, upgrade to 2.42.2; For 2.43.x, upgrade to 2.43.4; For 2.44.x, upgrade to 2.44.1; For 2.45.x, upgrade to 2.45.1
- 3. On Fedora 40, update Git via: sudo dnf update git
- 4. On Debian/Ubuntu, update Git via: sudo apt update && sudo apt install git (or add the Git PPA for newer versions)
- 5. Verify the fix by checking: git --version to confirm the new version is installed
- 6. As a temporary mitigation when cloning untrusted local repositories, use: git clone --no-local <repo> or git clone file://<repo> to avoid hardlink optimization
Generated from the published advisory — verify against the referenced sources before acting.
We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950.
Get the upgrade done
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2024-32021 — 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-32021 in production — separate from our analysis above.
Know something about CVE-2024-32021?
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.
What this is
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.
What belongs here
- 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