Loading vulnerability…
CVE-2015-3193 is a cryptographic calculation flaw in OpenSSL 1.0.2 releases before 1.0.2e on x86_64 platforms. The x86_64 Montgomery squaring implementation used by BN_mod_exp incorrectly propagates carries, causing incorrect modular-exponentiation results. The erroneous output can aid private-key recovery attacks against applications using Diffie-Hellman or ephemeral Diffie-Hellman cipher suites. Elliptic-curve algorithms are not affected.
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 moderate-severity OpenSSL x86_64 cryptographic implementation flaw: incorrect carry propagation in Montgomery squaring used by BN_mod_exp can leak private-key information during attacks against Diffie-Hellman or ephemeral Diffie-Hellman cipher suites. It affects OpenSSL 1.0.2 releases before 1.0.2e on x86_64. Red Hat states its shipped OpenSSL versions in RHEL 5, 6, and 7, plus listed JBoss products, are not affected.
A prior OpenSSL vulnerability mentioned only as a comparison to CVE-2017-3732; the content does not provide substantive technical details about it.
Referenced only for comparison as a vulnerability with impact similar to CVE-2017-3738.
A prior vulnerability referenced solely as a similar but separate issue; no further technical details are provided in this content.
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.