CVE-2021-21300 is a vulnerability in Git affecting versions from 2.14.2 up to the fixed releases, where a specially crafted repository containing symbolic links and files using clean/smudge filters (such as Git LFS) can trigger the execution of a just-checked out script during a clone operation on case-insensitive file systems (NTFS, HFS+, APFS). This is due to insufficient validation of symlinks and filter interactions, particularly on Windows and macOS systems where Git LFS is configured by default. The vulnerability is present in the Git component bundled with Xcode prior to version 12.5.
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.
git config --global core.symlinks false) and avoid configuring clean/smudge filters such as Git LFS globally before cloning. Additionally, avoid cloning repositories from untrusted sources.Patch, then assume compromise.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository demonstrates a proof-of-concept exploit for CVE-2021-21300, a vulnerability in Git (versions 2.14.2 to 2.30.1) affecting case-insensitive filesystems (Windows/macOS). The exploit leverages symbolic links and Git LFS filters to inject a malicious 'post-checkout' hook into the victim's .git/hooks directory. The repository contains a .gitattributes file to trigger LFS processing, a directory 'A' with files mimicking legitimate content, and a file 'A/post-checkout' which is intended to be executed as a malicious hook. The README.md provides a detailed explanation of the vulnerability, attack workflow, and possible defenses. No actual exploit script is present, but the structure and instructions clearly demonstrate how to set up the attack. The exploit is local, requiring the victim to clone the repository under specific conditions, after which arbitrary code execution is possible via the malicious hook.
This repository contains a single Metasploit module (git_lfs_clone_command_exec.rb) that exploits CVE-2021-21300, a vulnerability in Git clients supporting delay-capable clean/smudge filters (such as Git LFS) on case-insensitive file systems (MacOS, Windows). The exploit works by serving a malicious Git repository over HTTP. When a victim clones this repository, the exploit leverages Git LFS and symbolic links to place a malicious 'post-checkout' hook in the .git/hooks directory of the victim's local repository. This hook contains a shell payload (typically a reverse shell or arbitrary command) that is executed automatically upon checkout. The module is weaponized, allowing the attacker to easily customize the payload. The main attack vector is network-based, requiring the victim to clone the attacker's repository. The endpoints of interest are the HTTP path to the malicious repository and the file path of the malicious Git hook. The module is operational and ready for use within the Metasploit framework.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.