Loading vulnerability…
CVE-2020-5260 is a vulnerability in Git affecting versions prior to the patched releases on April 14th, 2020. The vulnerability arises from improper handling of specially-crafted URLs containing encoded newlines, which can inject unintended values into the credential helper protocol stream. This allows an attacker to trick Git into sending credentials intended for one host to a different, attacker-controlled host. The issue is triggered when a malicious URL is processed by Git, such as during a 'git clone' operation, especially in automated systems or submodule handling where URLs may not be visible to the user.
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 is a Proof-of-Concept (PoC) exploit for CVE-2020-5260, a credential leak vulnerability in Git. The repository contains a Go web server (main.go) that can be deployed to Heroku. The server exposes two main HTTP endpoints: '/' (the root) and '/test/'. The root endpoint is designed to receive requests from a git client performing a 'git clone' operation with a specially crafted URL. When accessed, it logs all HTTP headers and any Basic Auth credentials provided by the client, demonstrating the credential leak. The '/test/' endpoint is a simple test handler that returns 'OK!'. The README provides detailed instructions for deploying the PoC to Heroku and for triggering the vulnerability using a crafted git clone command. The repository does not contain any weaponized payloads; it is strictly a PoC for demonstrating the vulnerability. No hardcoded IP addresses or domains are present, but the Heroku app URL is intended to be customized by the user. The exploit targets vulnerable versions of Git across platforms.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.