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.
This vulnerability carries a LOW severity rating with a CVSS v3.1 score of 3.9, requiring local system access to exploit but requires specific conditions to be met though user interaction is required requiring only low-level privileges . The vulnerability impacts limited integrity, and limited availability for affected systems. Impacting 2 products from git-scm, from fedoraproject organizations running these solutions should prioritize assessment and patching.
Reported in 2024, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2024-05-14T19:15:12.240
2026-01-06T17:01:55.127
Analyzed
CVSSv3.1: 3.9 (LOW)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | git-scm | git | < 2.39.4 | Yes |
| Application | git-scm | git | < 2.40.2 | Yes |
| Application | git-scm | git | < 2.42.2 | Yes |
| Application | git-scm | git | < 2.43.4 | Yes |
| Application | git-scm | git | 2.41.0 | Yes |
| Application | git-scm | git | 2.44.0 | Yes |
| Application | git-scm | git | 2.45.0 | Yes |
| Operating System | fedoraproject | fedora | 40 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For git-scm's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.