CVE-2013-5123 is a software supply-chain vulnerability in Python Pip before version 1.5 affecting the deprecated mirroring feature invoked with -M or --use-mirrors. The feature discovered package mirrors through unsecured DNS queries and retrieved packages over plaintext HTTP without adequate authenticity verification. Pip would then unpack the retrieved package and typically execute its installation logic, creating a trust boundary failure in the package acquisition path. Upstream addressed the issue in pip 1.5 by removing the mirroring options entirely.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An insecure software download vulnerability in python-pip mirroring support where packages could be fetched over plaintext HTTP without authenticity checks, with mirror discovery performed via insecure DNS queries.
Insecure mirroring issue in pip; CVE-2013-4266 was rejected in favor of CVE-2013-5123.
Insecure mirroring vulnerability related to pip; the discussion indicates CVE-2013-5123 was assigned after CVE-2013-4266 had been proposed for the same issue.
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.