CVE-2016-9015
Published: 11 January 2017
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.
Notes
| Author | Note |
|---|---|
| seth-arnold | I'm marking our packages 'not-affected' due to upstream version notes. |
Priority
Status
| Package | Release | Status |
|---|---|---|
|
python-urllib3 Launchpad, Ubuntu, Debian |
precise |
Does not exist
|
| trusty |
Not vulnerable
|
|
| upstream |
Released
(1.18.1)
|
|
| xenial |
Not vulnerable
|
|
| yakkety |
Not vulnerable
|
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 3.7 |
| Attack vector | Network |
| Attack complexity | High |
| Privileges required | None |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | Low |
| Integrity impact | None |
| Availability impact | None |
| Vector | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |