CVE-2016-6329 is a cryptographic weakness in OpenVPN when it is configured to use a 64-bit block cipher for tunnel encryption, notably Blowfish in CBC mode. Because the cipher has a 64-bit block size, long-lived sessions that encrypt large volumes of traffic under the same key become susceptible to a birthday-bound block-collision attack known as Sweet32. In practical terms, an attacker able to observe a sufficiently large amount of ciphertext from the same OpenVPN session can exploit repeated block collisions to recover portions of cleartext from the protected traffic, as demonstrated against HTTP carried over OpenVPN. The issue is not a flaw in authentication or key exchange logic, but a weakness caused by continued use of legacy 64-bit block ciphers in long-duration encrypted sessions.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A long-known weakness in an outdated cipher configuration referenced as affecting weak tunnel settings in some Android VPN apps.
A vulnerability related to 64-bit block ciphers in TLS, referenced in test output showing the evaluated setup is not vulnerable.
Unknown
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.