CVE-2013-1629: Input Validation
First published: Tue May 28 2013(Updated: )
It was reported [1],[2] that pip, a package installer for Python modules, would retrieve code to install in an insecure manner. When pip is used to install a module, that code is retrieved from the internet and then, in the presence of setup.py, is executed. If pip is used as root (e.g. "sudo pip install [module]"), then this code is executed with root permissions. Because pip does not do TLS certificate verification, or package verification, it is trivial for an attacker to perform a MitM attack and cause the user attempting to install a module to execute arbitrary code. As of version 1.3, pip provides SSL certificate verification over HTTPS [3],[4]. [1] <a href="https://github.com/pypa/pip/issues/425">https://github.com/pypa/pip/issues/425</a> [2] <a href="http://www.reddit.com/r/Python/comments/17rfh7/warning_dont_use_pip_in_an_untrusted_network_a/">http://www.reddit.com/r/Python/comments/17rfh7/warning_dont_use_pip_in_an_untrusted_network_a/</a> [3] <a href="https://github.com/pypa/pip/pull/791/files">https://github.com/pypa/pip/pull/791/files</a> [4] <a href="http://www.pip-installer.org/en/latest/logic.html#ssl-certificate-verification">http://www.pip-installer.org/en/latest/logic.html#ssl-certificate-verification</a>
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| pip/pip | <1.3 | 1.3 |
| redhat/python-pip | <1.3 | 1.3 |
| pip/pywasm3 | <1.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/pypa/pip/issues/425
- http://www.reddit.com/r/Python/comments/17rfh7/warning_dont_use_pip_in_an_untrusted_network_a/
- https://github.com/pypa/pip/pull/791/files
- http://www.pip-installer.org/en/latest/logic.html#ssl-certificate-verification
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=968060
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=968061
- https://access.redhat.com/security/cve/CVE-2013-1629
- https://pip.pypa.io/en/latest/news.html
- https://github.com/pypa/pip/pull/791
- https://github.com/pypa/pip/pull/789
- https://bugzilla.redhat.com/show_bug.cgi?id=968059
- http://www.pip-installer.org/en/latest/installing.html
- http://www.pip-installer.org/en/latest/news.html#changelog
- https://nvd.nist.gov/vuln/detail/CVE-2013-1629
- https://github.com/advisories/GHSA-g3p5-fjj9-h8gj (Advisory)
- https://github.com/pypa/advisory-database/tree/main/vulns/pip/PYSEC-2013-8.yaml
- http://www.reddit.com/r/Python/comments/17rfh7/warning_dont_use_pip_in_an_untrusted_network_a
Frequently Asked Questions
What is the severity of CVE-2013-1629?
CVE-2013-1629 is rated as high severity due to its potential to execute arbitrary code when pip is used insecurely.
How do I fix CVE-2013-1629?
To fix CVE-2013-1629, upgrade pip to version 1.3 or later.
What software is affected by CVE-2013-1629?
CVE-2013-1629 affects pip versions earlier than 1.3.
Can CVE-2013-1629 be exploited in a trusted network?
CVE-2013-1629 can still be exploited in a trusted network if malicious code is executed during the pip installation.
What is the impact of CVE-2013-1629?
The impact of CVE-2013-1629 includes unauthorized execution of code with root privileges if pip is used with sudo.
- agent/type
- agent/first-publish-date
- agent/remedy
- agent/weakness
- agent/description
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-g3p5-fjj9-h8gj
- alias/CVE-2013-1629
- agent/software-canonical-lookup
- agent/references
- agent/severity
- agent/last-modified-date
- agent/softwarecombine
- agent/author
- collector/redhat-bugzilla
- source/Red Hat
- agent/event
- collector/github-advisory
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-cve
- source/NVD
- package-manager/pip
- package-manager/redhat
- vendor/pypa
- canonical/pip/pywasm3