CVE-2018-20225 is a dependency-confusion issue in pip's package-index resolution behavior. When pip is configured with --extra-index-url, it considers package versions across the configured indexes and selects the highest version. If an organization intends to retrieve a private package but that package name is not already present on the public index, an attacker can publish a package with the same name and a higher version to the public index, causing pip to select the attacker-controlled package. The behavior has also been characterized as intended pip functionality, making secure index configuration central to preventing exposure.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A pip dependency-confusion issue affecting use of the --extra-index-url option. pip can select a higher-versioned package from the public index instead of the intended private package when that package name is absent from the public index, allowing an attacker to publish an arbitrary higher-versioned package.
A pip package installation behavior issue (dependency confusion) where using --extra-index-url (or equivalent configuration) can cause pip to select and install an attacker-controlled package from a public index (e.g., PyPI) over the intended private package, if the attacker publishes the same package name with a higher version.
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.