CVE-2013-2037: httplib2 incorrectly checks SSL certificate

CVE-2013-2037 · Severity: low · CVSS 3.1 · Published 2014-01-18

httplib2 0.7.2, 0.8, and earlier, after an initial connection is made, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

Technologies: httplib2 (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2013-2037 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2013-2037 being exploited in the wild.
How severe is CVE-2013-2037?
Low severity, with a CVSS score of 3.1, published 18 January 2014.
Which products and versions are affected?
httplib2 (PyPI) ECOSYSTEM:introduced=0,fixed=0.10.1, ECOSYSTEM:introduced=0,fixed=0.9.
Is there a fix for CVE-2013-2037?
Yes. httplib2 (PyPI): upgrade to 0.10.1, 0.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2013-2037?
Check whether you run httplib2 (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

  • httplib2 (PyPI): upgrade to 0.10.1, 0.9 or later
    pip install "httplib2>=0.10.1"

Affected products

  • httplib2 (PyPI) ECOSYSTEM:introduced=0,fixed=0.10.1, ECOSYSTEM:introduced=0,fixed=0.9

Identifiers

  • CVE-2013-2037
  • GHSA-q48q-77qv-cf9p
  • PYSEC-2014-81

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