CVE-2013-1629
Pypa Pip vulnerability
pip before 1.3 uses HTTP to retrieve packages from the PyPI repository, and does not perform integrity checks on package contents, which allows man-in-the-middle attackers to execute arbitrary code via a crafted response to a "pip install" operation.
Affected products
Pip. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Pypa Pip runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- www.pip-installer.org/en/latest/installing.html · Vendor Advisory
- www.pip-installer.org/en/latest/news.html#changelog · Vendor Advisory
- github.com/pypa/pip/pull/791/files · Patch
- www.reddit.com/r/Python/comments/17rfh7/warning_dont_use_pip_in_an_untrusted_network_a/ · Exploit
- bugzilla.redhat.com/show_bug.cgi?id=968059 · Third Party Advisory
- github.com/pypa/pip/issues/425 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2013-1629
- github.com/advisories/GHSA-g3p5-fjj9-h8gj
- nvd.nist.gov/vuln/detail/CVE-2013-1629
- cve.org/CVERecord?id=CVE-2013-1629
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.