CVE-2022-4450: Double free in OpenSSL PEM_read_bio_ex
- Vendors
- OpenSSL Software FoundationStormshield
CVE-2022-4450 is a double-free vulnerability in OpenSSL PEM parsing. A specially crafted PEM input containing zero payload bytes causes PEM_read_bio_ex() to return failure while leaving its header output argument pointing to an already-freed buffer. If the caller subsequently frees that buffer, a double free occurs, most likely crashing the application. Directly affected wrappers include PEM_read_bio() and PEM_read(); affected indirect callers include PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file(). The OpenSSL asn1parse utility is also affected. Internal callers that do not free the header after parsing fails, including PEM_read_bio_TYPE() functions and the decoders introduced in OpenSSL 3.0, are not vulnerable through those calls.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
An attacker who can supply malicious PEM input to an affected parsing path can most likely crash the consuming application, causing denial of service. Network-reachable exploitation is possible when an application exposes the vulnerable parsing functionality to remote input. Code execution and information disclosure are not established consequences; Red Hat assesses neither for its affected products.
Mitigation
If you can’t patch tonight, do this now.
Until patched, restrict the ability to submit untrusted PEM input and limit access to services exposing affected PEM parsing functionality. Call paths that do not free the returned header pointer after PEM_read_bio_ex() fails do not trigger this double free; review application error handling to identify exposure. These measures do not replace installing the fix.
Remediation
Patch, then assume compromise.
Install vendor-fixed OpenSSL packages or update the affected application's bundled OpenSSL component. Fixed upstream releases include OpenSSL 1.1.1t and 3.0.8. Distribution backports include OpenSSL 1.1.1k-9.el8_7 for RHEL 8, 1.1.1k-9.el8_6 for RHEL 8.6 EUS, 3.0.1-47.el9_1 for RHEL 9, and 3.0.1-46.el9_0 for RHEL 9.0 EUS. For Rust openssl-src, fixed releases are 111.25.0 for the 1.1.1 branch and 300.0.12 for the 3.0 branch. Apply product-specific updates for embedded copies, including affected EDK2 packages. Restart services linked to OpenSSL or reboot after updating.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2022-4450 exploited in the wild?
- As of Nov 6, 2026, Mallory has no reports of CVE-2022-4450 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2022-4450?
- As of Nov 6, 2026, Mallory has found no public exploit for CVE-2022-4450.
- Is there a patch for CVE-2022-4450?
- Install vendor-fixed OpenSSL packages or update the affected application's bundled OpenSSL component. Fixed upstream releases include OpenSSL 1.1.1t and 3.0.8.
- What products are affected by CVE-2022-4450?
- OpenSSL Software Foundation Openssl and Stormshield Network Security.
- How severe is CVE-2022-4450?
- CVE-2022-4450 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 28.6% (98th percentile) as of Nov 6, 2026.
Recent activity
43 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.