CVE-2013-4314: PyOpenSSL Mishandles NUL Byte In Certificate Subject Alternative Name

CVE-2013-4314 · Severity: low · CVSS 3.1 · Published 2013-09-30

The X509Extension in pyOpenSSL before 0.13.1 does not properly handle a '\0' character in a domain name in the Subject Alternative Name field of an X.509 certificate, which allows man-in-the-middle attackers to spoof arbitrary SSL servers via a crafted certificate issued by a legitimate Certification Authority.

Technologies: pyopenssl (PyPI). Vendors: PyPI.

Quick answers

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

  • pyopenssl (PyPI): upgrade to 0.13.1 or later
    pip install "pyopenssl>=0.13.1"

Affected products

  • pyopenssl (PyPI) ECOSYSTEM:introduced=0,fixed=0.13.1

Identifiers

  • CVE-2013-4314
  • GHSA-6748-36qp-fx6r
  • PYSEC-2013-31

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