CVE-2014-9365: Medium severity Python Python vulnerability

Published Dec 11, 2014
·
Updated

Alex Gaynor reports:

""" When Python's standard library HTTP clients (httplib, urllib, urllib2, xmlrpclib) are used to access resources with HTTPS, by default the certificate is not checked against any trust store, nor is the hostname in the certificate checked against the requested host. It was possible to configure a trust root to be checked against, however there were no faculties for hostname checking.

This made MITM attacks against the HTTP clients trivial, and violated RFC 2818 (http://tools.ietf.org/html/rfc2818#section-3).

Python 2.7.9 has been issued to resolve this issue. It is also resolved in 3.4.3, which has not yet been released. """

CVE request: http://seclists.org/oss-sec/2014/q4/1022

Other sources

The HTTP clients in the (1) httplib, (2) urllib, (3) urllib2, and (4) xmlrpclib libraries in CPython (aka Python) 2.x before 2.7.9 and 3.x before 3.4.3, when accessing an HTTPS URL, do not (a) check the certificate against a trust store or verify that the server hostname matches a domain name in the subject's (b) Common Name or (c) subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

MITRE

Affected Software

90 affected componentsFixes available
redhat/Python<2.7.9
2.7.9
redhat/Python<3.4.3
3.4.3
Python Python=2.0
Python Python=2.0.1
Python Python=2.1
Python Python=2.1.1
Python Python=2.1.2
Python Python=2.1.3
Python Python=2.2
Python Python=2.2.1
Python Python=2.2.2
Python Python=2.2.3
Python Python=2.3.1
Python Python=2.3.2
Python Python=2.3.3
Python Python=2.3.4
Python Python=2.3.5
Python Python=2.3.7
Python Python=2.4.1
Python Python=2.4.2
Python Python=2.4.3
Python Python=2.4.4
Python Python=2.4.6
Python Python=2.5.1
Python Python=2.5.2
Python Python=2.5.3
Python Python=2.5.4
Python Python=2.5.6
Python Python=2.5.150
Python Python=2.6.1
Python Python=2.6.2
Python Python=2.6.3
Python Python=2.6.4
Python Python=2.6.5
Python Python=2.6.6
Python Python=2.6.7
Python Python=2.6.8
Python Python=2.6.2150
Python Python=2.6.6150
Python Python=2.7.1
Python Python=2.7.1-rc1
Python Python=2.7.2-rc1
Python Python=2.7.3
Python Python=2.7.4
Python Python=2.7.5
Python Python=2.7.6
Python Python=2.7.7
Python Python=2.7.8
Python Python=2.7.1150
Python Python=2.7.1150
Python Python=2.7.2150
Python Python=3.0
Python Python=3.0.1
Python Python=3.1
Python Python=3.1.1
Python Python=3.1.2
Python Python=3.1.3
Python Python=3.1.4
Python Python=3.1.5
Python Python=3.1.2150
Python Python=3.2
Python Python=3.2-alpha
Python Python=3.2.0
Python Python=3.2.1
Python Python=3.2.2
Python Python=3.2.3
Python Python=3.2.4
Python Python=3.2.5
Python Python=3.2.6
Python Python=3.2.2150
Python Python=3.3
Python Python=3.3-beta2
Python Python=3.3.0
Python Python=3.3.1
Python Python=3.3.1-rc1
Python Python=3.3.2
Python Python=3.3.3
Python Python=3.3.3-rc1
Python Python=3.3.3-rc2
Python Python=3.3.4
Python Python=3.3.4-rc1
Python Python=3.3.5
Python Python=3.3.5-rc1
Python Python=3.3.5-rc2
Python Python=3.3.6-rc1
Python Python=3.4-alpha1
Python Python=3.4.0
Python Python=3.4.1
Python Python=3.4.2
Apple iOS and macOS<=10.10.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/Python to a version that resolves this vulnerability.

    Fixed in 2.7.9
  2. Upgrade

    Upgrade redhat/Python to a version that resolves this vulnerability.

    Fixed in 3.4.3
  3. Upgrade

    Upgrade CPython (Python) to a version that resolves this vulnerability.

    Fixed in 2.7.9
  4. Upgrade

    Upgrade CPython (Python) to a version that resolves this vulnerability.

    Fixed in 3.4.3

Event History

Dec 11, 2014
Data Sourced
via Red Hat·10:55 AM
DescriptionSeverityAffected Software
Dec 12, 2014
CVE Published
via MITRE·11:00 AM
Data Sourced
via MITRE·11:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2014-9365?

CVE-2014-9365 is considered a moderate severity vulnerability due to its potential to allow man-in-the-middle attacks.

2

How do I fix CVE-2014-9365?

To fix CVE-2014-9365, upgrade Python to version 2.7.9 or 3.4.3 or later.

3

Which Python versions are affected by CVE-2014-9365?

CVE-2014-9365 affects Python versions 2.x before 2.7.9 and 3.x before 3.4.3.

4

What is the impact of CVE-2014-9365?

The impact of CVE-2014-9365 is that HTTPS connections may be insecure, as certificate validation is not performed.

5

Is there a workaround for CVE-2014-9365?

There is no recommended workaround for CVE-2014-9365 other than upgrading to a secure version of Python.

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