CVE-2016-9015: Urllib3 Incorrect Certificate Validation

CVE-2016-9015 · Severity: low · CVSS 3 · Published 2017-01-11

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.

Technologies: urllib3 (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2016-9015 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2016-9015 being exploited in the wild.
How severe is CVE-2016-9015?
Low severity, with a CVSS score of 3, published 11 January 2017.
Which products and versions are affected?
urllib3 (PyPI) ECOSYSTEM:introduced=1.17,fixed=1.18.1.
Is there a fix for CVE-2016-9015?
Yes. urllib3 (PyPI): upgrade to 1.18.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2016-9015?
Check whether you run urllib3 (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • urllib3 (PyPI): upgrade to 1.18.1 or later
    pip install "urllib3>=1.18.1"

Affected products

  • urllib3 (PyPI) ECOSYSTEM:introduced=1.17,fixed=1.18.1

Identifiers

  • CVE-2016-9015
  • GHSA-v4w5-p2hg-8fh6
  • PYSEC-2017-98

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.