Loading vulnerability…
CVE-2022-4304 is a timing side-channel vulnerability in OpenSSL's RSA private-key decryption implementation. Observable differences in decryption processing time can act as an oracle and enable a Bleichenbacher-style adaptive chosen-ciphertext attack over the network. The issue affects RSA decryption across multiple padding modes, including PKCS#1 v1.5, RSA-OAEP, and RSASVE. In TLS deployments that use RSA key exchange, an attacker who has observed a legitimate handshake can submit a very large number of crafted trial ciphertexts to the server, measure response timing, and use the resulting side-channel information to recover the original plaintext, such as the TLS pre-master secret.
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.
18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A timing oracle vulnerability in OpenSSL RSA decryption.
Timing side channel in RSA.
A timing oracle vulnerability in OpenSSL RSA decryption at the TLS level, related to Marvin-style attacks.
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.