Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
DROWN used a server still speaking the obsolete SSLv2 protocol as a decryption oracle against modern TLS sessions protected by the same RSA key, affecting a third of HTTPS sites in 2016.

What Is the DROWN Attack?
DROWN — Decrypting RSA with Obsolete and Weakened eNcryption — was disclosed on 1 March 2016 as CVE-2016-0800. It is a cross-protocol attack: an attacker records a modern TLS session and then decrypts it by making queries to a completely different server, provided that server still supports SSLv2 and uses the same RSA key or certificate.
That last condition is what caught people out. A properly configured, modern web server with SSLv2 long disabled was still vulnerable if the same certificate was installed on a mail server, a load balancer, or a forgotten test host that had never been updated. At disclosure, the research team estimated that around one third of all HTTPS servers were affected.
SSLv2 dates from 1995 and was known to be broken by 1996. Nobody used it deliberately. It survived because disabling it was a configuration step that administrators had no reason to think about, and because default builds of some software left it enabled. Nothing in day-to-day operation depended on it, nothing alerted on it, and it sat there for twenty years.
SSLv2 contains a padding oracle: the protocol’s export-grade cipher modes and its error handling allow an attacker to learn, from a server’s response, whether a guessed RSA-encrypted block had valid padding. This is a variant of the Bleichenbacher attack from 1998.
The attack proceeds by capturing a target TLS session that used RSA key exchange, then sending many thousands of modified versions of its encrypted pre-master secret to the SSLv2 server. The responses gradually reveal the plaintext. The general form required around 40,000 captured TLS connections and tens of thousands of SSLv2 queries, followed by substantial computation — the researchers reported a cost of roughly 440 US dollars on rented cloud computing.
A second variant, Special DROWN (CVE-2016-0703), exploited a specific OpenSSL bug and was far worse: one captured session, a few thousand queries, and under a minute on a single machine.
DROWN is remembered less for its mechanics than for its structural point. Security properties do not belong to a server; they belong to a key. If an RSA private key is installed in several places, the weakest of those places determines the strength of all of them.
That principle applies well beyond SSLv2. A wildcard certificate deployed across the estate means any one compromised host exposes every service using it. A certificate shared between a hardened production cluster and an unmaintained staging box inherits staging’s security. This is a recurring finding in infrastructure assessments and it is almost always a surprise to the people being assessed.
DROWN belongs to the same decade of TLS research as BEAST, FREAK, Logjam, POODLE, and CRIME and BREACH. Collectively they moved the industry from “TLS is enabled” to “which version, which cipher suites, which key exchange, and where else is this key”.
Protocol and certificate inventory review across the whole estate, not just the web tier, forms part of our infrastructure security testing services.
Rarely, because SSLv2 has been removed from maintained software and disabled almost everywhere. It remains worth checking on legacy mail servers, embedded appliances, and industrial systems that have not been reconfigured in a decade. The underlying lesson about private key reuse across systems of differing security posture is very much still current.
Because the attack targets the RSA key, not the service. If the same certificate and private key are installed on both the web server and a mail server that still supports SSLv2, an attacker can use the mail server as a decryption oracle against sessions captured from the web server. The web server’s own configuration is irrelevant.
Yes, for sessions that use it. TLS 1.3 removed RSA key exchange altogether in favour of ephemeral Diffie-Hellman, so there is no encrypted pre-master secret for an oracle to attack and recorded traffic cannot be decrypted later by obtaining the key. The vulnerable configuration only arises where RSA key exchange is still permitted.
It makes the private key’s exposure equal to the weakest system holding it. Compromise of any host with the key allows impersonation of every service covered by the certificate, and protocol weaknesses on one host can undermine the others, as DROWN showed. Issue separate certificates per trust boundary, and keep an inventory of where each key lives.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.