CVE-2024-32004 is an arbitrary code execution vulnerability in Git's handling of specially crafted local repositories during cloning. An attacker can prepare a local repository that causes attacker-controlled code to execute when it is cloned using a vulnerable Git version. Fixes are available in Git 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An upstream Git vulnerability mentioned as background for the Dulwich issue. The reference states that Git fixes existed but were not propagated into Dulwich's separately implemented submodule functionality; it does not separately describe this vulnerability's mechanics or affected versions.
A locally exploitable vulnerability requiring user interaction, with potential high impact to confidentiality, integrity, and availability, as characterized by the supplied CVSS v3.0 vector.
A vulnerability identified as CVE-2024-32004, covered by a CentOS 7 local security check. The supplied CVSS vectors indicate a local attack requiring user interaction, with high confidentiality, integrity, and availability impact.
A vulnerability addressed by the OpenShift Container Platform 4.12.65 security update; no technical details are provided in the advisory.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.