CVE-2017-3731 is an integer-underflow flaw in OpenSSL SSL/TLS packet processing that permits a truncated packet to cause an out-of-bounds read. It affects OpenSSL 1.1.0 through 1.1.0c on 32-bit hosts when CHACHA20/POLY1305 is used, and OpenSSL 1.0.2 through 1.0.2j on 32-bit hosts when RC4-MD5 is enabled and used. The invalid read usually terminates the affected SSL/TLS client or server process.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An OpenSSL out-of-bounds read issue in which a truncated packet could cause a crash.
An OpenSSL out-of-bounds read condition in which a truncated packet could crash the affected process.
An OpenSSL out-of-bounds read condition in which a truncated packet could crash the affected process. The advisory supplies updated packages.
An OpenSSL integer-underflow flaw resulting in an out-of-bounds read, allowing a remote attacker to crash affected 32-bit TLS/SSL clients or servers when the RC4-MD5 cipher suite is in use.
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.