Описание
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2018-1000807
- https://github.com/pyca/pyopenssl/pull/723
- https://github.com/pyca/pyopenssl/commit/e73818600065821d588af475b024f4eb518c3509
- https://access.redhat.com/errata/RHSA-2019:0085
- https://github.com/pypa/advisory-database/tree/main/vulns/pyopenssl/PYSEC-2018-23.yaml
- https://usn.ubuntu.com/3813-1
- http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00014.html
Пакеты
pyopenssl
< 17.5.0
17.5.0
Связанные уязвимости
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.
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.
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.
Python Cryptographic Authority pyopenssl version prior to version 17.5 ...
