CVE-2024-32020 [Low] | Security Vulnerability in Git

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, local clones may end up hardlinking files into the target repository's object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a "proper" clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. 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.

EDB-ID	Source	Kind	Published	Link
—	nvd_ref	exploit_tag		Exploit-DB ↗

EDB-ID

Source

Kind

Published

Link

—

nvd_ref

exploit_tag

Exploit-DB ↗

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-01-18	0.05%	0.17%	+0.11%
2	2026-01-02	0.05%	0.05%	+0.01%
3	2025-12-10	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-01-18

0.05%

0.17%

+0.11%

2026-01-02

0.05%

+0.01%

2025-12-10

—

0.05%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
3.9	3.1	LOW	`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:L` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	0.8	2.7	[email protected]
3.3	3.1	LOW	`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	1.8	1.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

3.9

3.1

LOW

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:L Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

0.8

2.7

[email protected]

3.3

3.1

LOW

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

1.8

1.4

[email protected]

OS Trackers for CVE-2024-32020

vendor	priority	summary	link
`alpine`	—	CVE-2024-32020: 1 source package rows (git); 75 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 68.	https://security.alpinelinux.org/vuln/CVE-2024-32020
`debian`	not yet assigned	CVE-2024-32020 not yet assigned priority: Debian including 1 source packages (git), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1.	https://security-tracker.debian.org/tracker/CVE-2024-32020
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2024-32020
`suse`	medium	CVE-2024-32020 severity moderate: SUSE including 150 source package names (0.0.17-1.1:git-core-2.43.0-150600.3.3.1, 0.1.6-1.2:git-2.43.0-150600.3.3.1, …), 418 product×package rows across 63 product lines (Container bci/gcc, Container bci/golang, … (63 product lines)): Fixed 344, Known Not Affected 74.	https://www.suse.com/security/cve/CVE-2024-32020/
`ubuntu`	medium	CVE-2024-32020 medium priority: Ubuntu including 1 source packages (git), 7 status rows across 7 suites (bionic, focal, jammy, mantic, noble, upstream, xenial): released 6, not-affected 1.	https://ubuntu.com/security/CVE-2024-32020

Affected software / configurations for CVE-2024-32020

Vendor	Product	Version	Raw CPE
git-scm	git	< 2.39.4	cpe:2.3:a:git-scm:git::::::::
git-scm	git	>= 2.40.0, < 2.40.2	cpe:2.3:a:git-scm:git::::::::
git-scm	git	>= 2.42.0, < 2.42.2	cpe:2.3:a:git-scm:git::::::::
git-scm	git	>= 2.43.0, < 2.43.4	cpe:2.3:a:git-scm:git::::::::
git-scm	git	2.41.0	cpe:2.3:a:git-scm:git:2.41.0:::::::*
git-scm	git	2.44.0	cpe:2.3:a:git-scm:git:2.44.0:::::::*
git-scm	git	2.45.0	cpe:2.3:a:git-scm:git:2.45.0:::::::*
fedoraproject	fedora	40	cpe:2.3:o:fedoraproject:fedora:40:::::::*

References for CVE-2024-32020

URL	Tags
http://www.openwall.com/lists/oss-security/2024/05/14/2	Mailing List Third Party Advisory
https://github.com/git/git/commit/1204e1a824c34071019fe106348eaa6d88f9528d	Patch
https://github.com/git/git/commit/9e65df5eab274bf74c7b570107aacd1303a1e703	Patch
https://github.com/git/git/security/advisories/GHSA-5rfh-556j-fhgj	Exploit Vendor Advisory
https://lists.fedoraproject.org/archives/list/[email protected]/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/	Mailing List Third Party Advisory

URL

CVE-2024-32020 | Cloning local Git repository by untrusted user allows the untrusted user to modify objects in the cloned repository at will

Public exploit references (Exploit-DB) for CVE-2024-32020

Exploit prediction scoring system (EPSS) score for CVE-2024-32020

Common vulnerability scoring system (CVSS) metrics for CVE-2024-32020

Weakness enumeration for CVE-2024-32020

OS Trackers for CVE-2024-32020

Affected software / configurations for CVE-2024-32020

References for CVE-2024-32020