CVE-2024-32020Public exploit

Repository corruption via cross-owner object hardlinks

Published May 14, 2024 · Updated Feb 13, 2025

Improper permission preservation in Git allows local users to corrupt cloned repository objects through unsafe local clones. The copy_or_link_directory path can hardlink object files from a source repository owned by another user, leaving those files writable through the source after cloning completes. Exploitation requires a victim to perform a local clone from an attacker-controlled repository on the same disk; subsequent object rewriting damages integrity and can make the clone unusable.

CVSS severity3.9
Low
EPSS probability0.52%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper permission preservation in Git allows local users to corrupt cloned repository objects through unsafe local clones. The copy_or_link_directory path can hardlink object files from a source repository owned by another user, leaving those files writable through the source after cloning completes. Exploitation requires a victim to perform a local clone from an attacker-controlled repository on the same disk; subsequent object rewriting damages integrity and can make the clone unusable.

The record

CVE
CVE-2024-32020
Published
May 14, 2024
Updated
Feb 13, 2025
Vendor
Git
Product
Git
Classifications
CWE-281, T1565.001
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 14, 2024CVE publishedPublication date reported by the CVE source.
  2. Feb 13, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <2.39.4
  2. Affected versionversion=< 2.39.4
  3. Affected versionversion=>= 2.40.0, < 2.40.2
  4. Affected versionversion=2.40.0 <2.40.2
  5. Affected versionversion== 2.41.0
  6. Affected versionversion=2.41.0
  7. Affected versionversion=>= 2.42.0, < 2.42.2
  8. Affected versionversion=2.42.0 <2.42.2
  9. Affected versionversion=>= 2.43.0, < 2.43.4
  10. Affected versionversion=2.43 <2.43.4
  11. Affected versionversion== 2.44.0
  12. Affected versionversion=2.44.0
  13. Affected versionversion== 2.45.0
  14. Affected versionversion=2.45.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Git · Gitversion=0 <2.39.4; version=< 2.39.4; version=>= 2.40.0, < 2.40.2; version=2.40.0 <2.40.2; version== 2.41.0; version=2.41.0; version=>= 2.42.0, < 2.42.2; version=2.42.0 <2.42.2; version=>= 2.43.0, < 2.43.4; version=2.43 <2.43.4; version== 2.44.0; version=2.44.0; version== 2.45.0; version=2.45.0

Published CVSS scores

3.9GitHub, Inc.CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:L
3.3NIST NVDCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-281Improper Preservation of Permissions
T1565.001Stored Data Manipulation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo