HighGHSA-p28m-34f6-967qCVE-2018-1000807PYSEC-2018-23

PyOpenSSL Use-After-Free vulnerability

Published 10 Oct 2018 · Updated 15 Oct 2024

Is your project on an affected pyopenssl?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<17.5.0
Fixed in
17.5.0
Update to the fixed version for your release line, for example:pip install 'pyopenssl>=17.5.0'

Details

It was discovered that pyOpenSSL incorrectly handled memory when handling X509 objects. A remote attacker could use this issue to cause pyOpenSSL to crash, resulting in a denial of service, or possibly execute arbitrary code. This attack appears to be exploitable via Depends on the calling application and if it retains a reference to the memory. This vulnerability appears to have been fixed in 17.5.0.

Is GHSA-p28m-34f6-967q 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-2013-4314PyOpenSSL Mishandles NUL Byte In Certificate Subject Alternative Name · 17 May 2022
  • HighCVE-2018-1000808Pyopenssl Incorrect Memory Management · 10 Oct 2018
pyopenssl security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.