CVE-2024-32020: 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 fi...

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

Metrics

CVSS 3.1

3.3/10

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

EPSS Probability

0.52%

40.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-281

Affected Software

Vendor	Product	Versions
Git-Scm	Git	< 2.39.4
Git-Scm	Git	>= 2.40.0, < 2.40.2
Git-Scm	Git	>= 2.42.0, < 2.42.2
Git-Scm	Git	>= 2.43.0, < 2.43.4
Git-Scm	Git	2.41.0
Git-Scm	Git	2.44.0
Git-Scm	Git	2.45.0
Fedoraproject	Fedora	40

References

http://www.openwall.com/lists/oss-security/2024/05/14/2Mailing List, Third Party Advisory
https://github.com/git/git/commit/1204e1a824c34071019fe106348eaa6d88f9528dPatch
https://github.com/git/git/commit/9e65df5eab274bf74c7b570107aacd1303a1e703Patch
https://github.com/git/git/security/advisories/GHSA-5rfh-556j-fhgjExploit, Vendor Advisory
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/Mailing List, Third Party Advisory
http://www.openwall.com/lists/oss-security/2024/05/14/2Mailing List, Third Party Advisory
https://github.com/git/git/commit/1204e1a824c34071019fe106348eaa6d88f9528dPatch
https://github.com/git/git/commit/9e65df5eab274bf74c7b570107aacd1303a1e703Patch
https://github.com/git/git/security/advisories/GHSA-5rfh-556j-fhgjExploit, Vendor Advisory
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/Mailing List, Third Party Advisory

Timeline

Published: May 14, 2024
Last Modified: Jun 17, 2026
Status: Analyzed

Frequently Asked Questions

What is CVE-2024-32020?

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.

How severe is CVE-2024-32020?

CVE-2024-32020 has a CVSS score of 3.3/10 (LOW severity). The EPSS model estimates a 0.52% probability of exploitation in the next 30 days.

How do I fix CVE-2024-32020?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.