CVE-2018-1000807: pyopenssl Use After Free Vulnerability

pyopenssl Updated 02 Oct 2025

Summary

08/10/2018
Yes i
High
8.1

CVE-2018-1000807: Python Cryptographic Authority pyopenssl version prior to version 17.5.0 contains a CWE-416: Use After Free vulnerability in X509 object handling that can result in Use after free can lead to possible denial of service o... Affects pyopenssl versions < 17.5.0. Fixed in 17.5.0. How to fix ↓

Also tracked for

The same CVE-2018-1000807 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

pyopenssl is a Python library that provides a high-level interface to the OpenSSL library. It allows Python programs to easily access the full range of cryptographic ciphers, message digests, and other related functionality. The library is widely used in various applications for secure communication and encryption. However, versions prior to 17.5.0 are affected by a Use After Free vulnerability in the handling of X509 objects. This vulnerability can potentially lead to denial of service or remote code execution if the calling application retains a reference to the freed memory.

Vulnerability Detail

The Use After Free vulnerability in pyopenssl arises from improper handling of X509 objects. When a reference to an X509 object is retained by the calling application after it has been freed, subsequent use of that reference can lead to unexpected behavior. An attacker could potentially exploit this vulnerability to cause a denial of service or execute arbitrary code, depending on the context in which the vulnerable code is used. The vulnerability has been assigned the identifier CVE-2018-1000807.

How To Fix

Minimum fixed version

17.5.0

This is the first release that contains the fix.

pip install --upgrade "pyopenssl==17.5.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability other than upgrading to a fixed version of pyopenssl.

Conclusion

The Use After Free vulnerability in pyopenssl can have serious security implications, potentially leading to denial of service or remote code execution. It is crucial to upgrade to version 17.5.0 or later to mitigate this vulnerability. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for pyopenssl →

Share this vulnerability

FAQ

pyopenssl is a Python library that provides a high-level interface to the OpenSSL library, enabling Python programs to utilize various cryptographic functions.

A Use After Free vulnerability occurs when a program continues to use a memory reference after it has been freed, leading to potential security issues and unexpected behavior.

The Use After Free vulnerability in pyopenssl can result in denial of service or remote code execution, depending on the context in which the vulnerable code is used.

To fix this vulnerability, it is recommended to upgrade pyopenssl to version 17.5.0 or later.

No, there is no known workaround for this vulnerability other than upgrading to a fixed version of pyopenssl.

Related vulnerabilities

Recent vulnerabilities recorded for pyopenssl.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Minimum fixed version

17.5.0

This is the first release that contains the fix.

pip install --upgrade "pyopenssl==17.5.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback