Skip to content
Fencer Intel
high 8.1

CVE-2018-1000807 json

PyOpenSSL Use-After-Free vulnerability

published 8y ago modified 4mo ago also GHSA-p28m-34f6-967q , PYSEC-2018-23 , EUVD-2018-0123

cvss
8.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.1%
EPSS 4.1% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

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 or remote code execution.. This attack appear 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.

Patch / fix

  • pypi pyopenssl 17.5.0
  • pyopenssl pyopenssl 17.5.0
  • pyopenssl Debian 14, Debian 13, Debian 12 17.5.0-1

debian advisories DEBIAN-CVE-2018-1000807

  • pyopenssl Ubuntu 16.04 LTS 0.15.1-2ubuntu0.2

ubuntu advisories UBUNTU-CVE-2018-1000807

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • pyOpenSSL openstack 13 17.5.0-1.el7ost
  • python2-pyOpenSSL openstack 13 17.5.0-1.el7ost

red hat advisories RHSA-2019:0085

  • python-pyOpenSSL SLES for SAP 12 SP5, SLES 12 SP5 17.1.0-4.26.1
  • crowbar OpenStack Cloud Crowbar 8 5.0+git.1551088826.010c0399-3.12.2
  • ardana-db OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1550589454.df2e733-3.22.2
  • ardana-ses OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1554145115.63a4cf2-1.17.2
  • crowbar-ha OpenStack Cloud Crowbar 8 5.0+git.1553248675.7e103ea-3.14.2
  • ardana-heat OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1552935705.e9a92b3-3.9.2
  • ardana-nova OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1551718533.227cb9e-3.26.2
  • ardana-swift OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1551502730.f4d219d-3.24.2

suse advisories SUSE-SU-2024:3749-1SUSE-SU-2024:1626-1SUSE-RU-2019:1161-1SUSE-SU-2018:4063-1

  • py-openssl Alpine 3.8, Alpine 3.7, Alpine 3.6 17.5.0-r0

alpine advisories ALPINE-CVE-2018-1000807

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2018-1000807 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1000807 updated cvss 8.1

pyOpenSSL: Use-after-free in X509 object handling

  • Red Hat OpenStack Platform 10 (Newton) pyOpenSSL, python-pyOpenSSL Red Hat OpenStack Platform 12 (Pike) python-pyOpenSSL Red Hat Storage 3 pyOpenSSL Red Hat Virtualization 4 python-pyOpenSSL, python2-pyOpenSSL
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 13.0 pyOpenSSL 17.5.0-1.el7ost, python2-pyOpenSSL 17.5.0-1.el7ost
    fixed: vendor fix RHSA-2019:0085
  • Red Hat Enterprise Linux 5 pyOpenSSL Red Hat Enterprise Linux 6 pyOpenSSL Red Hat Enterprise Linux 7 pyOpenSSL Red Hat Enterprise Linux 8 python3-pyOpenSSL Red Hat OpenStack Platform 14 (Rocky) python2-pyOpenSSL
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.08% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi pyopenssl
<17.5.0
17.5.0

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.