CVE-2024-32021

Local Git clone may hardlink arbitrary user-readable files into the new repository's "objects/" directory

HIGH
7.1
CVSS Score
Published: May 14, 2024 at 07:15 PM UTC
Updated: June 17, 2026 at 07:29 AM UTC
4 products affected across 4 vendorsDebian LinuxFedoraGit

Using git by git?

Get instant alerts when new vulnerabilities affect git - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 1%
SSVC
PoC

Description

Git 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.39.42.40.0 ≤ v < 2.40.22.42.0 ≤ v < 2.42.22.43.0 ≤ v < 2.43.42.41.02.44.02.45.0
Git· Gitrubygems
60%
v < 2.39.4v < 2.40.2v < 2.42.2v < 2.43.42.40.0 ≤ v < 2.40.22.41.0 ≤ v < 2.41.12.42.0 ≤ v < 2.42.22.43.0 ≤ v < 2.43.42.44.0 ≤ v < 2.44.12.45.0 ≤ v < 2.45.12.40.02.41.02.42.02.43.02.44.02.45.0= 2.41.0= 2.44.0= 2.45.0
Affected range stops below 2.39.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.40.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.41.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.42.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.43.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.44.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.45.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-547

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card