CVE-2016-0800

UnknownEPSS 82.11%

Last modified

CVE-2016-0800 is a vulnerability of currently unknown severity. The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to send a ServerVerify message before establishing that a client possesses certain plaintext RSA data, which makes it easier for remote attackers to decrypt TLS ciphertext data by leveraging a Bleichenbacher RSA padding oracle, aka a "DROWN" attack.. EPSS estimates a 82.11% chance of exploitation in the next 30 days.

Description

The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to send a ServerVerify message before establishing that a client possesses certain plaintext RSA data, which makes it easier for remote attackers to decrypt TLS ciphertext data by leveraging a Bleichenbacher RSA padding oracle, aka a "DROWN" attack.

Metrics

EPSS Probability
82.11%

99.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
OpensslOpenssl1.0.1
OpensslOpenssl1.0.1a
OpensslOpenssl1.0.1b
OpensslOpenssl1.0.1c
OpensslOpenssl1.0.1d
OpensslOpenssl1.0.1e
OpensslOpenssl1.0.1f
OpensslOpenssl1.0.1g
OpensslOpenssl1.0.1h
OpensslOpenssl1.0.1i
OpensslOpenssl1.0.1j
OpensslOpenssl1.0.1k
OpensslOpenssl1.0.1l
OpensslOpenssl1.0.1m
OpensslOpenssl1.0.1n
OpensslOpenssl1.0.1o
OpensslOpenssl1.0.1p
OpensslOpenssl1.0.1q
OpensslOpenssl1.0.1r
OpensslOpenssl1.0.2
OpensslOpenssl1.0.2a
OpensslOpenssl1.0.2b
OpensslOpenssl1.0.2c
OpensslOpenssl1.0.2d
OpensslOpenssl1.0.2e
OpensslOpenssl1.0.2f
PulsesecureClientAll versions
PulsesecureSteel Belted RadiusAll versions

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-0800?
The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to send a ServerVerify message before establishing that a client possesses certain plaintext RSA data, which makes it easier for remote attackers to decrypt TLS ciphertext data by leveraging a Bleichenbacher RSA padding oracle, aka a "DROWN" attack.
How severe is CVE-2016-0800?
Severity scoring for CVE-2016-0800 is pending analysis. The EPSS model estimates a 82.11% probability of exploitation in the next 30 days.
How do I fix CVE-2016-0800?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-0800?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST