CVE-2024-12797 is an improper server-authentication validation flaw in OpenSSL's RFC 7250 Raw Public Key (RPK) support. In affected OpenSSL 3.2, 3.3, and 3.4 releases, a TLS or DTLS client configured with SSL_VERIFY_PEER may allow a handshake to complete when the server's RPK does not match an expected public key, rather than aborting the handshake. Applications that explicitly retrieve the verification result with SSL_get_verify_result() and reject failed verification remain protected. The flaw was introduced with the initial RPK implementation in OpenSSL 3.2.
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.
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An issue where RFC7250 handshakes with unauthenticated servers do not abort as expected in OpenSSL.
A vulnerability where RFC7250 handshakes with unauthenticated servers do not abort as expected in OpenSSL.
Unknown
A vulnerability in OpenSSL where RFC7250 handshakes with unauthenticated servers do not abort as expected.
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.