Loading vulnerability…
CVE-2016-2179 is a denial-of-service vulnerability in OpenSSL's DTLS implementation. DTLS buffers out-of-order handshake messages until they can be processed. A flaw in the buffer-lifecycle logic can leave messages in the queue after handshake completion even though they are no longer needed. An attacker can retain approximately 15 unnecessary buffered messages per DTLS connection; with the default maximum message size of 100 KB, this consumes approximately 1.5 MB of additional memory per connection. The condition affects OpenSSL versions before 1.1.0, including affected 1.0.1 and 1.0.2 releases.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A low-severity OpenSSL denial-of-service vulnerability in DTLS buffered message handling, affecting OpenSSL 1.0.2 and 1.0.1 DTLS users.
OpenSSL DTLS memory exhaustion denial-of-service vulnerability caused by buffered handshake messages not being removed after completion.
OpenSSL DTLS fragment-buffer memory leak resulting in denial of service.
OpenSSL DTLS fragment-buffer memory leak resulting in denial of service.
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.