Loading vulnerability…
CVE-2014-9390 affects multiple Git-related clients and libraries, including Git, Mercurial, Apple Xcode, libgit2, EGit, and JGit, on Windows and OS X case-insensitive filesystems. The vulnerability arises from improper handling and validation of repository tree entries that can be interpreted as .git/config through alternate representations, including use of ignorable Unicode code points, an 8.3-style git~1/config representation, or mixed-case path variants. When a victim interacts with a malicious remote repository, the crafted tree can cause the client to write or treat attacker-controlled content as the repository's .git/config file. Because Git configuration can specify external commands and behaviors, this can lead to arbitrary command execution on the client system.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module: 'git_client_command_exec.rb', which implements an exploit for CVE-2014-9390. The exploit targets vulnerable Git and Mercurial clients on case-insensitive file systems (Windows, macOS) by serving a malicious HTTP server that mimics a Git or Mercurial repository. When a victim clones or interacts with this repository, specially crafted files and hooks are delivered, potentially leading to arbitrary code execution on the victim's machine. The module supports both Unix (command payloads) and Windows (Powershell payloads), and allows customization of the malicious repository's URI endpoints. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The only file in the repository is a Ruby script, which is the main entry point for the exploit.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.