Skip to content
Noroxi
CVE-2024-32002· NVD / CVE Program· CNA GitHub_M

Git's recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code Execution

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, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a `.git/` directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. 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. If symbolic link support is disabled in Git (e.g. via `git config --global core.symlinks false`), the described attack won't work. As always, it is best to avoid cloning repositories from untrusted sources.

CriticalCVSS 9.0 · v3.1—Proof of concept Fix available
Published
May 14, 2024
Updated
Jun 17, 2026
EPSS
29.2% · 98th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

45

Plan

Add it to your regular patch cycle.

CVSS
36 / 40 · 9.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
9 / 30 · 29.2%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
9.0
CNA · GitHub_M
9.1
0.1 point gap

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

Affected systems

VendorProduct
gitgit

Affected versions

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

  • git gitbefore 2.39.4
  • git git2.40.0 and later · before 2.40.2
  • git git2.42.0 and later · before 2.42.2
  • git git2.43.0 and later · before 2.43.4
  • git git2.41.0
  • git git2.44.0
  • git 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

+96

Same product

git: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-25648The package git before 1.11.0 are vulnerable to Command Injection via git argument injection.
    40Plan
  • CVE-2025-48385Git alllows arbitrary file writes via bundle-uri parameter injection
    34Monitor
  • CVE-2008-5517The web interface in git (gitweb) 1.5.x before 1.5.6 allows remote attackers to execute arbitrary commands via shell metacharacters related
    34Monitor
  • CVE-2020-5260malicious URLs may cause Git to present stored credentials to the wrong server
    33Monitor
  • CVE-2008-5516The web interface in git (gitweb) 1.5.x before 1.5.5 allows remote attackers to execute arbitrary commands via shell metacharacters related
    31Monitor
  • CVE-2008-3546Stack-based buffer overflow in the (1) diff_addremove and (2) diff_change functions in GIT before 1.5.6.4 might allow local users to execute
    31Monitor

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
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)
SUSE:git2.35.3-150300.10.39.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×50

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02024-07-29
Proof-of-concept repository on GitHubstars:22024-05-17
Proof-of-concept repository on GitHubstars:02024-05-17
Proof-of-concept repository on GitHubstars:5322024-05-17
Proof-of-concept repository on GitHubstars:182024-05-17
Proof-of-concept repository on GitHubstars:102024-05-18
Proof-of-concept repository on GitHubstars:02024-05-18
Proof-of-concept repository on GitHubstars:12024-05-18
Proof-of-concept repository on GitHubstars:1092024-05-18
Proof-of-concept repository on GitHubstars:02024-05-19
Proof-of-concept repository on GitHubstars:02024-05-19
Proof-of-concept repository on GitHubstars:02024-05-19

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.

  1. Published
  2. First PoC+2 d
  3. TodaySep 30, 2026+868 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

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

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

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

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

References

All records