Loading vulnerability…
A vulnerability in git-shell, affecting Git versions before 2.4.12 and various later branches before their respective patch releases, allows remote authenticated users to potentially gain elevated privileges. The issue arises when a repository name beginning with a dash ('-') is used, which may be interpreted as a command-line option rather than a positional argument, leading to unintended behavior and possible privilege escalation.
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 provides a proof-of-concept (PoC) environment for CVE-2017-8386, a vulnerability in git-shell (version 2.12.2) that allows sandbox bypass and remote command execution. The repository includes a Dockerfile to build a vulnerable Ubuntu 16.04 container with git 2.12.2 and an SSH server, and a docker-compose.yml to facilitate container management. The README.md details the setup and exploitation process: after configuring SSH access for the 'git' user, an attacker can connect via SSH and use the 'less' command (invoked through 'git-upload-archive --help') to execute arbitrary shell commands using the '!' feature in less, thus escaping the git-shell sandbox. The exploit is network-based, requiring SSH access to the target. The repository does not contain automated exploit scripts but provides all necessary steps and configuration files to reproduce the vulnerability and demonstrate the exploit manually.
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.