PyOpenSSL Mishandles NUL Byte In Certificate Subject Alternative Name
Published 17 May 2022 · Updated 24 Oct 2024
Is your project on an affected pyopenssl?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <0.13.1
- Fixed in
- 0.13.1
pip install 'pyopenssl>=0.13.1'Details
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.
Is GHSA-6748-36qp-fx6r in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected pyopenssl, and gives you the command that fixes it.
More advisories for pyopenssl
- HighCVE-2026-27459pyOpenSSL DTLS cookie callback buffer overflow · 16 Mar 2026
- LowCVE-2026-27448pyOpenSSL allows TLS connection bypass via unhandled callback exception in set_tlsext_servername_callback · 16 Mar 2026
- HighCVE-2018-1000807PyOpenSSL Use-After-Free vulnerability · 10 Oct 2018
- HighCVE-2018-1000808Pyopenssl Incorrect Memory Management · 10 Oct 2018
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2013-4314
- Linkgithub.com/pyca/pyopenssl/commit/6bbf44a00b35fb28df1f66aa194b2fe95eab1ab2
- Linkbugzilla.redhat.com/show_bug.cgi?id=1005325
- Packagegithub.com/pyca/pyopenssl
- Linkgithub.com/pypa/advisory-database/tree/main/vulns/pyopenssl/PYSEC-2013-31.yaml
- Linkmail.python.org/pipermail/pyopenssl-users/2013-September/000478.html
- Linklists.opensuse.org/opensuse-updates/2013-11/msg00015.html
- Linkwww.debian.org/security/2013/dsa-2763
- Linkwww.openwall.com/lists/oss-security/2013/09/06/2
- Linkwww.ubuntu.com/usn/USN-1965-1
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.