CVE-2016-2178 is a timing side-channel vulnerability in OpenSSL's DSA signing implementation. In dsa_sign_setup, the constant-time flag was not consistently preserved, allowing certain private-key-dependent DSA operations to execute through a non-constant-time code path. The behavior affects OpenSSL releases through 1.0.2h, including the affected 1.0.1 release branch. A cache-timing attack has demonstrated recovery of a private DSA key.
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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A low-severity OpenSSL vulnerability where the constant-time flag is not preserved during DSA signing, affecting OpenSSL 1.0.2 and 1.0.1.
OpenSSL side-channel vulnerability in DSA signing implementation allowing private key recovery via cache-timing attack.
An OpenSSL side-channel vulnerability caused by non-constant-time operations during DSA signature computation. A local attacker may recover another user or service's private DSA key on the same system.
An OpenSSL DSA-signature implementation flaw in which non-constant-time operations may expose another local user or service's private DSA key.
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.