CVE-2024-32020

lowpriority · track · 13EPSS 0.005 · 44 %ileDEEURUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.52% (44th) EPSS
CVSS 3.3 · low
Is it mine?
52 products
Check your exposure
Who says so?
5 sources
cnnvd · enisa_euvd · fstec_bdu · osv

EPSS · scored 2026-10-27

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.

01

cvss

Technical severity, 0–10. One row per scoring source.

3.9
010

base score 0–10 · higher = more severe · hover a vector to decode

v3.13.3lowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:Nprimary · NVD / NIST USexploitability 1.8 · impact 1.4
v3.13.9lowAV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:Lsecondary · FSTEC (BDU) RU
v3.13.9lowCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:Lsecondary · ENISA EU
v3.13.9lowCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:Lsecondary · security-advisories@github.comexploitability 0.8 · impact 2.7
v3.13.1lowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N/E:Usecondary · CVSS-BT (t0sche)
02

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
03

weaknesses

The CWE weakness classes this flaw belongs to.

04

affected products (52)

Products and version ranges known to be affected.

showing 20 of 52
05

advisories (3)

Vendor and ecosystem advisories describing this.

  • WID-SEC-W-2024-1125git: Mehrere SchwachstellenDeutsch2024-05-14csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer oder ein lokaler authentifizierter Angreiferkann mehrere Schwachstellen in git ausnutzen, um beliebigen Programmcode auszuführen und und die Sicherheitsmaßnahmen zu umgehen.

  • WID-SEC-W-2025-0794Juniper Junos Space: Mehrere SchwachstellenDeutsch2025-04-13csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Juniper Junos Space ausnutzen, um seine Privilegien zu erhöhen, um einen Denial of Service Zustand herbeizuführen und um andere, nicht näher spezifizierte Auswirkungen zu erzielen.

  • BIT-git-2024-32020Cloning local Git repository by untrusted user allows the untrusted user to modify objects in the cloned repository at will2024-05-24vendor · osvUS

    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.

06

also known as (4)

Other names and identifiers for this entity.

07

sources

Which sources assert this record, and when.

08

references (17)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan