Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2024-32020: Cloning local Git repository by untrusted user allows the untrusted user to modify objects in the cloned repository at will

Noroxi assessment

Priority: Monitor (action score 13/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.51% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: CBL Mariner 2.0 ARM 2.39.4-1; CBL Mariner 2.0 x64 2.39.4-1.

Low priority for now. Upgrade to CBL Mariner 2.0 ARM 2.39.4-1; CBL Mariner 2.0 x64 2.39.4-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

LowCVSS 3.3 · v3.1—No exploit Fix available
Published
May 14, 2024
Updated
Jun 17, 2026
EPSS
0.5% · 44th percentile

Report tools

JSON

Action score

13

Monitor

Low priority for now.

CVSS
13 / 40 · 3.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
3.3
CNA · GitHub_M
3.9
0.6 point gap

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-32020

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for git-scm records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
git-scmgit
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora40
  • git-scm git2.40.0 and later · before 2.40.2
  • git-scm git2.42.0 and later · before 2.42.2
  • git-scm git2.43.0 and later · before 2.43.4
  • git-scm gitbefore 2.39.4
  • git-scm git2.41.0
  • git-scm git2.44.0
  • git-scm git2.45.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • git git

    • = 2.45.0, = 2.44.0, >= 2.43.0, < 2.43.4, >= 2.42.0, < 2.42.2, = 2.41.0, >= 2.40.0, < 2.40.2, < 2.39.4affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8gitbefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8git-allbefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8git-corebefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8git-core-docbefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8git-credential-libsecretbefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8git-daemonbefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8git-emailbefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8git-guibefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8git-instawebbefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8git-subtreebefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8git-svnbefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8gitkbefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8gitwebbefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8perl-Gitbefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:8perl-Git-SVNbefore 2.43.5-1.el8_102.43.5-1.el8_10
AlmaLinux:9gitbefore 2.43.5-1.el9_42.43.5-1.el9_4
AlmaLinux:9git-allbefore 2.43.5-1.el9_42.43.5-1.el9_4
AlmaLinux:9git-corebefore 2.43.5-1.el9_42.43.5-1.el9_4
AlmaLinux:9git-core-docbefore 2.43.5-1.el9_42.43.5-1.el9_4
AlmaLinux:9git-credential-libsecretbefore 2.43.5-1.el9_42.43.5-1.el9_4
AlmaLinux:9git-daemonbefore 2.43.5-1.el9_42.43.5-1.el9_4
AlmaLinux:9git-emailbefore 2.43.5-1.el9_42.43.5-1.el9_4
AlmaLinux:9git-guibefore 2.43.5-1.el9_42.43.5-1.el9_4
AlmaLinux:9git-instawebbefore 2.43.5-1.el9_42.43.5-1.el9_4

+82

Same product

git-scm: all records

Other highest-scoring records for the same primary product.

  • CVE-2018-17456Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows r
    68This week
  • CVE-2025-48384Git allows arbitrary code execution through broken config quotingKEV
    63This week
  • CVE-2021-21300malicious repositories can execute remote code while cloning
    60This week

Published before and after this one in the same product

  • ← EarlierCVE-2023-29007Apr 25, 2023 · Arbitrary configuration injection via `git submodule deinit`
    33Monitor
  • ← EarlierCVE-2024-32004May 14, 2024 · Git vulnerable to Remote Code Execution while cloning special-crafted local repositories
    31Monitor
  • Later →CVE-2024-32021May 14, 2024 · Local Git clone may hardlink arbitrary user-readable files into the new repository's "objects/" directory
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
CBL Mariner 2.0 ARM2.39.4-1 · gitMicrosoft (MSRC)
CBL Mariner 2.0 x642.39.4-1 · gitMicrosoft (MSRC)
almalinux:git2.43.5-1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:git-all2.43.5-1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:git-core2.43.5-1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:git-core-doc2.43.5-1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:git-credential-libsecret2.43.5-1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:git-daemon2.43.5-1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:git-email2.43.5-1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:git-gui2.43.5-1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:git-instaweb2.43.5-1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:git-subtree2.43.5-1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:git-svn2.43.5-1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:gitk2.43.5-1.el9_4 · AlmaLinux:9Package registry (OSV)
alpine:git2.39.5-r0 · Alpine:v3.17Package registry (OSV)
debian:git1:2.39.5-0+deb12u1 · Debian:12Package registry (OSV)
opensuse:git2.35.3-150300.10.39.1 · openSUSE:Leap 15.5Package registry (OSV)
red hat:git0:2.43.5-1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-all0:2.43.5-1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-core0:2.43.5-1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-core-debuginfo0:2.43.5-1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-core-doc0:2.43.5-1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-credential-libsecret0:2.43.5-1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-credential-libsecret-debuginfo0:2.43.5-1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-daemon0:2.43.5-1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-daemon-debuginfo0:2.43.5-1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-debuginfo0:2.43.5-1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-debugsource0:2.43.5-1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:git-email0:2.43.5-1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:git0:2.43.5-1.el9_4 · Rocky Linux:9Package registry (OSV)

+1

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-281 · Improper Preservation of Permissions

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records