First published: Mon Oct 08 2018(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Pyopenssl Pyopenssl | <17.5.0 | |
Canonical Ubuntu Linux | =16.04 | |
Redhat Openstack | =13 | |
Redhat Enterprise Linux Desktop | =7.0 | |
Redhat Enterprise Linux Server | =7.0 | |
Redhat Enterprise Linux Workstation | =7.0 | |
redhat/pyOpenSSL | <17.5.0 | 17.5.0 |
debian/pyopenssl | 20.0.1-1 23.0.0-1 24.2.1-1 | |
pip/pyopenssl | <17.5.0 | 17.5.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this issue is CVE-2018-1000807.
The severity of CVE-2018-1000807 is high with a CVSS score of 8.1.
The affected software for CVE-2018-1000807 includes python Cryptographic Authority pyopenssl version prior to version 17.5.0.
The vulnerability can be exploited through the use after free vulnerability in X509 object handling, which can lead to possible denial of service or remote code execution.
You can find more information about CVE-2018-1000807 at the following references: [GitHub](https://github.com/pyca/pyopenssl/pull/723), [Ubuntu Security Notice](https://usn.ubuntu.com/3813-1/), [Red Hat Security Advisory](https://access.redhat.com/errata/RHSA-2019:0085).