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

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published: 2024-05-14T18:54:08.184Z

Updated: 2024-08-02T01:59:50.905Z

Reserved: 2024-04-09T15:29:35.937Z

Link: CVE-2024-32020

cve-icon Vulnrichment

Updated: 2024-08-02T01:59:50.905Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2024-05-14T19:15:12.240

Modified: 2024-06-10T18:15:32.080

Link: CVE-2024-32020

cve-icon Redhat

Severity : Low

Publid Date: 2024-05-14T00:00:00Z

Links: CVE-2024-32020 - Bugzilla