CVE-2024-32020
Git-Scm Git ≤ 2.39.4
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:LSummary
CVE-2024-32020 is a low-severity Improper Preservation of Permissions (CWE-281) vulnerability in Git-Scm Git. Its CVSS base score is 3.9 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-16 (Security and Privacy Attributes) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-29858
Vulnerability Data
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.…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 8 hardening rules · 3 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Associating and preserving security attributes (including permissions) with objects reduces the chance they are lost or weakened on copy/restore/share.
Enforcing approved authorizations for access directly stops objects from receiving or retaining less-restrictive permissions than intended.
Least-privilege assignments limit the blast radius when permissions are incorrectly relaxed during copy/restore/share operations.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing least-privilege permission policies and reviews directly prevents incorrect permission propagation on copy/restore/share operations.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Access-control policy defines how permissions must be preserved when objects are copied or shared.
Access-rights provisioning and review processes directly address the risk of overly permissive copied objects.
Privileged-access management includes rules for maintaining correct permissions on copied or restored data.
Information-access-restriction controls enforce least-privilege permissions that must be preserved during copy/restore operations.
Change-management procedures can require verification that permissions remain intact after modifications or restores.
Configuration baselines can embed permission settings, indirectly reducing the chance of incorrect preservation.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Windows Server 2019 (1 rule)
- V-205743 Windows Server 2019 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions. prevents CWE-281
Windows Server 2022 (2 rules)
- V-254393 Windows Server 2022 Active Directory Group Policy objects must have proper access control permissions. prevents CWE-281
- V-254395 Windows Server 2022 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions. prevents CWE-281