Skip to main content
No exploitation reportedFix available

CVE-2024-32465

No exploitation reported by the sources we read.

  • Published2024-05-14
  • Fixed in2.39.4
  • WeaknessCWE-22

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Git is a revision control system. The Git project recommends to avoid working in untrusted repositories, and instead to clone it first with `git clone --no-local` to obtain a clean copy. Git has specific protections to make that a safe operation even with an untrusted source repository, but vulnerabilities allow those protections to be bypassed. In the context of cloning local repositories owned by other users, this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for CVE-2024-32004 are not enough: For example, when obtaining a `.zip` file containing a full copy of a Git repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run within the context of that repository. 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. As a workaround, avoid using Git in repositories that have been obtained via archives from untrusted sources.

Timeline

dates in UTC
  1. 2024-05-1420:15CVE publishedNVD

Versions per branch

CISA-ADP · OSV · NVD
Git
BranchAffectedFixed in
2.39≥ 2.39.4*, < 2.39.42.39.4
2.45= 2.45.0no fix published
2.43≥ 2.43.0, ≤ 2.43.4no fix published
2.42≥ 2.42.0, ≤ 2.42.2no fix published
2.40≥ 2.40.0, ≤ 2.40.2no fix published
Git-scm git
BranchAffectedFixed in
2.45≥ 2.45.0, < 2.45.12.45.1
2.44≥ 2.44.0, < 2.44.12.44.1
2.43≥ 2.43.0, < 2.43.42.43.4
2.42≥ 2.42.0, < 2.42.22.42.2
2.41≥ 2.41.0, < 2.41.12.41.1
2.40≥ 2.40.0, < 2.40.22.40.2
2.39< 2.39.42.39.4
2.41= 2.41.0no fix published
2.44= 2.44.0no fix published
2.45= 2.45.0no fix published
Debian debian linux
BranchAffectedFixed in
10.0= 10.0no fix published
11.0= 11.0no fix published

1 more product in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • git
    Affected
    • = = 2.45.0no fix stated
    • = = 2.44.0no fix stated
    • = >= 2.43.0, < 2.43.4no fix stated
    • = >= 2.42.0, < 2.42.2no fix stated
    • = = 2.41.0no fix stated
    • = >= 2.40.0, < 2.40.2no fix stated
    • = < 2.39.4no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-06-26

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • gitWolfiall versions · fixed in 2.45.1-r0
  • gitUbuntu:Pro:18.04:LTSall versions · fixed in 1:2.17.1-1ubuntu0.18+esm1
  • gitUbuntu:Pro:16.04:LTSall versions · fixed in 1:2.7.4-0ubuntu1.10+esm8
  • gitUbuntu:24.04:LTSall versions · fixed in 1:2.43.0-1ubuntu7.1
  • gitUbuntu:22.04:LTSall versions · fixed in 1:2.34.1-1ubuntu1.11
  • gitUbuntu:20.04:LTSall versions · fixed in 1:2.25.1-1ubuntu3.12
  • gitTuxCare:Ubuntu:18.04all versions · fixed in 1:2.17.1-1ubuntu0.18+tuxcare.els3and 13 other packages
  • gitTuxCare:CentOS:8.5all versions · fixed in 2.27.0-1.el8.tuxcare.els5and 14 other packages

60 more package ranges on OSV.dev

Vendor advisories

  • CVE-2024-32465 Red Hat Product Security153 products fixed · 51 known affected

    git: additional local RCE

    emacs-git as a component of Red Hat Enterprise Linux 6 · emacs-git-el as a component of Red Hat Enterprise Linux 6 · git as a component of Red Hat Enterprise Linux 6 · +48 more

  • RHSA-2024:4368 Red Hat Product Security51 products fixed

    Red Hat Security Advisory: git security update

  • RHSA-2024:4083 Red Hat Product Security51 products fixed

    Red Hat Security Advisory: git security update

  • RHSA-2024:4084 Red Hat Product Security51 products fixed

    Red Hat Security Advisory: git security update

Full record on NVD

Fix

  1. Update Git to 2.39.4
  2. Vendor fix Red Hat Product Security RHSA-2024:4368 · 51 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  3. Workaround from the vendor Red Hat Product Security RHSA-2024:4368 · 51 productsTo reduce the risk of exploitation, users are advised to refrain from using Git in repositories obtained from archives sourced from untrusted origins. This precautionary measure helps to minimize exposure to potential security threats until the necessary patches can be applied.
  4. No fix planned, says the vendor Red Hat Product Security CVE-2024-32465 · 32 productsOut of support scope
  5. No fix planned, says the vendor Red Hat Product Security CVE-2024-32465 · 19 productsWill not fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2024-05-14
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-vm9j-46j9-qvq4

Frequently asked questions

What is CVE-2024-32465?

Git is a revision control system. The Git project recommends to avoid working in untrusted repositories, and instead to clone it first with `git clone --no-local` to obtain a clean copy. Git has specific protections to make that a safe operation even with an untrusted source repository, but vulnerabilities allow those protections to be bypassed. In the context of cloning local repositories owned by other users, this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for CVE-2024-32004 are not enough: For example, when obtaining a `.zip` file containing a full copy of a Git repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run within the context of that repository. 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. As a workaround, avoid using Git in repositories that have been obtained via archives from untrusted sources.

Is CVE-2024-32465 actively exploited?

Active exploitation of CVE-2024-32465 has not been confirmed. Its EPSS score was 1.0% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-32465?

CVE-2024-32465 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running git? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record