PyOpenSSL Use-After-Free vulnerability
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-1000807US | high8.1 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00014.htmlWEB
- https://access.redhat.com/errata/RHSA-2019:0085WEB
- https://github.com/pyca/pyopensslPACKAGE
- https://github.com/pyca/pyopenssl/commit/e73818600065821d588af475b024f4eb518c3509WEB
- https://github.com/pyca/pyopenssl/pull/723WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/pyopenssl/PYSEC-2018-23.yamlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2018-1000807ADVISORY
- https://usn.ubuntu.com/3813-1WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan