Vulnerabilities · 2016 · Python
CVE-2016-9015
Python Urllib3 vulnerability
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.
Affected products
Urllib3. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Python Urllib3 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.openwall.com/lists/oss-security/2016/10/27/6 · Mitigation
- www.securityfocus.com/bid/93941 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2016-9015
- web.archive.org/web/20210123184150/http://www.securityfocus.com/bid/93941
- github.com/urllib3/urllib3/commit/c32cdbc16a9634fa0f8c829d1270301570158715
- github.com/pypa/advisory-database/tree/main/vulns/urllib3/PYSEC-2017-98.yaml
- github.com/advisories/GHSA-v4w5-p2hg-8fh6
- nvd.nist.gov/vuln/detail/CVE-2016-9015
- cve.org/CVERecord?id=CVE-2016-9015
More vulnerabilities in Python products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.