CVE-2016-2107 is a timing-based padding-oracle flaw in OpenSSL AES-NI CBC MAC validation affecting OpenSSL releases before 1.0.1t and 1.0.2 releases before 1.0.2h. A constant-time padding-check rewrite introduced for the Lucky Thirteen fix did not verify that a decrypted record contained sufficient bytes for both the MAC and padding. This produces timing-distinguishable behavior during AES-CBC TLS, SSL, or DTLS record processing, allowing an affected server to act as a padding oracle.
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 valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
OpenSSL padding oracle vulnerability enabling man-in-the-middle decryption of AES-CBC traffic on AES-NI capable servers.
An OpenSSL flaw fixed by the Red Hat JBoss Core Services httpd 2.4.23 update.
An OpenSSL flaw fixed by the Red Hat JBoss Core Services httpd 2.4.23 update.
A timing side-channel flaw in OpenSSL AES-NI AES-CBC MAC checking that could enable remote recovery of plaintext from encrypted TLS/SSL or DTLS packets through a padding-oracle attack.
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.