CVE-2016-9015: Low severity red hat python3-urllib3 vulnerability

Published 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.

Affected Software

3 affected componentsFixes available
pip/urllib3>=1.17<=1.18
1.18.1
Python urllib3=1.17
Python urllib3=1.18

Event History

Jan 11, 2017
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Data Sourced
via NVD·04:59 PM
DescriptionSeverityWeaknessAffected Software
May 17, 2022
Advisory Published
03:05 AM

Frequently Asked Questions

1

What is the severity of CVE-2016-9015?

CVE-2016-9015 has been classified as a high severity vulnerability due to the potential for man-in-the-middle attacks and information leakage.

2

How do I fix CVE-2016-9015?

To mitigate CVE-2016-9015, update the urllib3 library to version 1.18.1 or later.

3

Which versions are affected by CVE-2016-9015?

CVE-2016-9015 affects urllib3 versions 1.17 and 1.18.

4

What types of attacks are possible with CVE-2016-9015?

CVE-2016-9015 can lead to man-in-the-middle attacks and potential information leakage.

5

Who is at risk due to CVE-2016-9015?

Users of urllib3 versions 1.17 and 1.18 with specific configurations are at risk due to CVE-2016-9015.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203