CVE-2024-32020
Git Hardlink Privilege Escalation Vulnerability
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.
INFO
Published Date :
May 14, 2024, 7:15 p.m.
Last Modified :
Nov. 21, 2024, 9:14 a.m.
Source :
[email protected]
Remotely Exploitable :
No
Impact Score :
2.7
Exploitability Score :
0.8
Public PoC/Exploit Available at Github
CVE-2024-32020 has a 1 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-32020.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
None
Dockerfile Go
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-32020 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-32020 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference http://www.openwall.com/lists/oss-security/2024/05/14/2 Added Reference https://github.com/git/git/commit/1204e1a824c34071019fe106348eaa6d88f9528d Added Reference https://github.com/git/git/commit/9e65df5eab274bf74c7b570107aacd1303a1e703 Added Reference https://github.com/git/git/security/advisories/GHSA-5rfh-556j-fhgj Added Reference https://lists.fedoraproject.org/archives/list/[email protected]/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/ -
CVE Modified by [email protected]
Jun. 10, 2024
Action Type Old Value New Value Added Reference GitHub, Inc. https://lists.fedoraproject.org/archives/list/[email protected]/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/ [No types assigned] Added Reference GitHub, Inc. http://www.openwall.com/lists/oss-security/2024/05/14/2 [No types assigned] -
CVE Received by [email protected]
May. 14, 2024
Action Type Old Value New Value Added 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. Added Reference GitHub, Inc. https://github.com/git/git/security/advisories/GHSA-5rfh-556j-fhgj [No types assigned] Added Reference GitHub, Inc. https://github.com/git/git/commit/1204e1a824c34071019fe106348eaa6d88f9528d [No types assigned] Added Reference GitHub, Inc. https://github.com/git/git/commit/9e65df5eab274bf74c7b570107aacd1303a1e703 [No types assigned] Added CWE GitHub, Inc. CWE-281 Added CVSS V3.1 GitHub, Inc. AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:L
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-32020 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-32020
weaknesses.