Loading vulnerability…
CVE-2022-4450 is a double-free vulnerability in OpenSSL's PEM parsing logic. The vulnerable function, PEM_read_bio_ex(), reads a PEM object from a BIO, parses the PEM name, header data, and payload, and returns decoded buffers to the caller. A specially crafted PEM file can be constructed with zero bytes of payload data. In that error condition, PEM_read_bio_ex() returns failure but may still populate the header output argument with a pointer to memory that has already been freed. If the caller subsequently frees that header buffer, a double free occurs. The wrapper functions PEM_read_bio() and PEM_read() are directly affected, and the issue is also reachable indirectly through other OpenSSL functionality that invokes PEM_read_bio_ex(), including PEM_X509_INFO_read_bio_ex(), SSL_CTX_use_serverinfo_file(), and the OpenSSL asn1parse command-line application. Some internal call sites are not affected because they do not free the header argument on failure.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.