Skip to main content
Mallory
MediumVulnerability

CVE-2016-0800: DROWN

Published Mar 1, 2016 · Updated 28 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.9Medium · v3
EPSS82.1%100th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Pulse SecureOpenSSL Software Foundation
IdentifiersCVE-2016-0800CWE-327

DROWN (Decrypting RSA with Obsolete and Weakened eNcryption) is a cross-protocol cryptographic attack that uses SSLv2 handshakes to decrypt TLS sessions. SSLv2 sends a ServerVerify message before establishing that the client possesses the required RSA plaintext, exposing a Bleichenbacher RSA padding oracle. An attacker can combine this oracle with weaknesses in EXPORT-grade encryption to recover TLS session secrets. Affected implementations include OpenSSL before 1.0.1s and the 1.0.2 branch before 1.0.2g, when configured to support vulnerable SSLv2 operation, as well as other SSLv2 implementations. A TLS service can be exposed even when it disables SSLv2 if another reachable service supports SSLv2 using the same RSA private key.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the confidentiality of intercepted TLS sessions using RSA key exchange, potentially exposing credentials and application data. Previously recorded non-forward-secure sessions can also be decrypted while a suitable SSLv2 oracle remains available. Passively recorded forward-secure sessions are not directly vulnerable. Separate legacy OpenSSL flaws can accelerate DROWN and enable stronger active man-in-the-middle attacks. DROWN does not directly recover the server's RSA private key or provide arbitrary code execution.

Mitigation

If you can’t patch tonight, do this now.

Disable SSLv2 entirely on every SSL/TLS endpoint, including mail services and other services sharing RSA keys with HTTPS endpoints. Do not rely solely on disabling EXPORT or other SSLv2 cipher suites: CVE-2015-3197 can permit negotiation of nominally disabled SSLv2 ciphers on unpatched OpenSSL servers. Restrict network access to affected services while updates are pending. Prefer TLS 1.2 or TLS 1.3 with forward-secure key exchange.

Remediation

Patch, then assume compromise.

Upgrade affected OpenSSL installations to a currently supported release incorporating the DROWN countermeasures. The original fixed releases were OpenSSL 1.0.1s and 1.0.2g, which disabled SSLv2 by default at build time and removed vulnerable SSLv2 EXPORT and 56-bit DES ciphers. For embedded or vendor-managed products, install the applicable vendor firmware or security update. Inventory every service sharing an RSA private key and ensure SSLv2 is disabled across all of them. Restart affected services after replacing their cryptographic libraries. Private-key regeneration is not required solely because of DROWN once all vulnerable services sharing the key have been addressed.

Public exploits

Exploits

No validated public exploits yet. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenSSL Software FoundationOpensslapplication
Pulse SecureClientapplication
Pulse SecureSteel Belted Radiusapplication
FAQ

Frequently asked questions

Is CVE-2016-0800 exploited in the wild?
As of Oct 25, 2026, Mallory has no reports of CVE-2016-0800 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2016-0800?
As of Oct 25, 2026, Mallory has found no public exploit for CVE-2016-0800.
Is there a patch for CVE-2016-0800?
Upgrade affected OpenSSL installations to a currently supported release incorporating the DROWN countermeasures. The original fixed releases were OpenSSL 1.0.1s and 1.0.2g, which disabled SSLv2 by default at build time and removed vulnerable SSLv2 EXPORT and 56-bit DES ciphers.
What products are affected by CVE-2016-0800?
Pulse Secure Client, OpenSSL Software Foundation Openssl, and Pulse Secure Steel Belted Radius.
How severe is CVE-2016-0800?
CVE-2016-0800 has a CVSS v3 score of 5.9 (Medium) and an EPSS score of 82.1% (100th percentile) as of Oct 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.