Safety vulnerability ID: 35691
The information on this page was manually curated by our Cybersecurity Intelligence Team.
Urllib3 version 1.18.1 includes a fix for CVE-2016-9015: Versions 1.17 and 1.18 of the Python urllib3 library suffer from a vulnerability that can cause them, in certain configurations, to not correctly validate TLS certificates. This places users of the library with those configurations at risk of man-in-the-middle and information leakage attacks. This vulnerability affects users using versions 1.17 and 1.18 of the urllib3 library, who are using the optional PyOpenSSL support for TLS instead of the regular standard library TLS backend, and who are using OpenSSL 1.1.0 via PyOpenSSL. This is an extremely uncommon configuration, so the security impact of this vulnerability is low.
https://www.openwall.com/lists/oss-security/2016/10/27/6
Latest version: 2.2.1
HTTP library with thread-safe connection pooling, file post, and more.
Versions 1.17 and 1.18 of the Python urllib3 library suffer from a vulnerability that can cause them, in certain configurations, to not correctly validate TLS certificates. This places users of the library with those configurations at risk of man-in-the-middle and information leakage attacks. This vulnerability affects users using versions 1.17 and 1.18 of the urllib3 library, who are using the optional PyOpenSSL support for TLS instead of the regular standard library TLS backend, and who are using OpenSSL 1.1.0 via PyOpenSSL. This is an extremely uncommon configuration, so the security impact of this vulnerability is low.
MLIST:[oss-security] 20161027 CVE-2016-9015: Python urllib3 1.17 and 1.18 certificate verification failure: http://www.openwall.com/lists/oss-security/2016/10/27/6
BID:93941: http://www.securityfocus.com/bid/93941
Scan your Python project for dependency vulnerabilities in two minutes
Scan your application