Loading vulnerability…
CVE-2016-2105 is an integer-overflow vulnerability in OpenSSL's EVP_EncodeUpdate() Base64-encoding function. When an application directly supplies a very large binary input buffer to the API, an overflow in length checking can result in a heap-based buffer overflow and heap corruption. OpenSSL internal use via PEM_write_bio* is not affected because those call paths enforce input-length bounds. The issue affects OpenSSL releases before 1.0.1t and 1.0.2 releases before 1.0.2h.
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.
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
OpenSSL heap corruption vulnerability in EVP_EncodeUpdate during Base64 encoding with very large untrusted input.
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.
OpenSSL EVP_EncodeUpdate integer-overflow buffer overflow that can cause denial of service or possible arbitrary code execution.
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.