CVE-2016-2182 is an out-of-bounds write vulnerability in OpenSSL's BN_bn2dec() decimal-conversion function. In vulnerable releases, BN_bn2dec() fails to check an error return from BN_div_word(). When processing an excessively large BIGNUM, this failure can leave an internal value unreduced and cause writes beyond the bn_data buffer. The issue affects OpenSSL releases 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.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A low-severity OpenSSL vulnerability involving an out-of-bounds write in BN_bn2dec(), affecting OpenSSL 1.0.2 and 1.0.1.
OpenSSL out-of-bounds write in BN_bn2dec when handling overly large BIGNUM values, potentially affecting certificate or CRL printing from untrusted sources.
OpenSSL BN_bn2dec() out-of-bounds write with potential application crash or arbitrary code execution.
OpenSSL BN_bn2dec() out-of-bounds write with potential application crash or 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.