First published: Wed Jan 11 2017(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/urllib3 | >=1.17<=1.18 | 1.18.1 |
Python 3 urllib3 | =1.17 | |
Python 3 urllib3 | =1.18 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-9015 has been classified as a high severity vulnerability due to the potential for man-in-the-middle attacks and information leakage.
To mitigate CVE-2016-9015, update the urllib3 library to version 1.18.1 or later.
CVE-2016-9015 affects urllib3 versions 1.17 and 1.18.
CVE-2016-9015 can lead to man-in-the-middle attacks and potential information leakage.
Users of urllib3 versions 1.17 and 1.18 with specific configurations are at risk due to CVE-2016-9015.