Name | CVE-2018-20225 |
Description | An issue was discovered in pip (all versions) because it installs the version with the highest version number, even if the user had intended to obtain a private package from a private index. This only affects use of the --extra-index-url option, and exploitation requires that the package does not already exist in the public index (and thus the attacker can put the package there with an arbitrary version number). NOTE: it has been reported that this is intended functionality and the user is responsible for using --extra-index-url securely |
Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
Source Package | Release | Version | Status |
---|
python-pip (PTS) | jessie, jessie (lts) | 1.5.6-5+deb8u2 | vulnerable |
| stretch (security), stretch (lts), stretch | 9.0.1-2+deb9u2 | vulnerable |
| buster | 18.1-5 | vulnerable |
| bullseye | 20.3.4-4+deb11u1 | vulnerable |
| bookworm | 23.0.1+dfsg-1 | vulnerable |
| sid, trixie | 24.3.1+dfsg-1 | vulnerable |
The information below is based on the following data on fixed versions.
Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
---|
python-pip | source | (unstable) | (unfixed) | unimportant | | |
Notes
https://cowlicks.website/posts/arbitrary-code-execution-from-pips-extra-index-url.html
pip is inherently affected by malicious packages, use packages from Debian instead :-)