CVE-2022-4450 is a double-free vulnerability in OpenSSL PEM_read_bio_ex() and its PEM_read_bio() and PEM_read() wrappers. A PEM file with a zero-byte payload can cause PEM_read_bio_ex() to return failure while leaving its header output argument pointing to memory that has already been freed. If the calling application frees that header pointer, a double free occurs. Indirect callers, including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file(), can also be affected when their calling behavior frees the header after the failure path. The OpenSSL asn1parse command-line application is affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
41 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability addressed by the CIQ edk2 security update for Rocky Linux 8.6.
A double-free vulnerability in OpenSSL after calling PEM_read_bio_ex.
Unknown
A vulnerability addressed through the Red Hat Enterprise Linux 9 el9/flatpak-sdk container-image update; no technical flaw details are provided.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.