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 |
---|---|---|
redhat/python-pip | <1.3 | 1.3 |
pypa pip | <1.3 | |
pip/pip | <1.3 | 1.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-1629 is rated as high severity due to its potential to execute arbitrary code when pip is used insecurely.
To fix CVE-2013-1629, upgrade pip to version 1.3 or later.
CVE-2013-1629 affects pip versions earlier than 1.3.
CVE-2013-1629 can still be exploited in a trusted network if malicious code is executed during the pip installation.
The impact of CVE-2013-1629 includes unauthorized execution of code with root privileges if pip is used with sudo.