Double Free in OpenSSL
CVE-2022-4450
The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue.
Vulnerability class: Double Free
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS: 0.286 (98.1th percentile), scored .
Moderate probability of exploitation in the next 30 days — watch for active exploitation reports. 98th percentile — 98.1% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.204 · newest: 0.286 · change: +0.081
Affected products
- OpenSSL — versions 3.0.0, 1.1.1
- Stormshield Network Security
Weakness classification (CWE)
Public proof-of-concept exploits
References
- www.openssl.org/news/secadv/20230207.txt (vendor-advisory, Vendor Advisory)
- git.openssl.org/gitweb/ (Patch, patch, Vendor Advisory)
- git.openssl.org/gitweb/ (Patch, patch, Vendor Advisory)
- security.gentoo.org/glsa/202402-08
- af854a3a-2127-422b-91ae-364da2661108
- 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
- 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
- 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
- 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
- 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
Frequently asked questions
- What is CVE-2022-4450?
- CVE-2022-4450 is a high-severity vulnerability in OpenSSL, classified under Double Free. CVSS score: 7.5/10. Published 2023-02-08.
- How severe is CVE-2022-4450?
- High severity. CVSS v3 base score is 7.5 out of 10.
- Is CVE-2022-4450 known to be exploited?
- 21 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.