Skip to content
Noroxi
NVD / CVE Program· CNA redhat

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…

MediumCVSS 5.9 · v3.0—Weaponized Fix available

Noroxi assessment

Priority: This week (action score 60/100)

  • A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
  • A ready-made attack tool exists and the flaw can be exploited over the network without an account, so priority is at least “This week”.
  • Probability of exploitation in the next 30 days: 82.1% (FIRST EPSS); higher than 99.6% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: nss (Debian:12) 3.13; openssl (Debian:12) 1.0.0c-2; openssl (Red Hat:enterprise_linux:5::client) 0:0.9.8e-39.el5_11.

Don’t wait for the next maintenance window. Upgrade to nss (Debian:12) 3.13; openssl (Debian:12) 1.0.0c-2; openssl (Red Hat:enterprise_linux:5::client) 0:0.9.8e-39.el5_11 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Mar 1, 2016
Updated
Jun 16, 2026
EPSS
82.1% · 99th percentile

Report tools

JSON

Action score

60

This week

Don’t wait for the next maintenance window.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
25 / 30 · 82.1%
Ready-made attack tool
12 / 60 · floor: at least 60

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Weaponized exploit exists
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2016-0800

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Check your server's TLS configurationRun the SSL check

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Check your server's TLS configurationRun the SSL check

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
opensslopenssl
pulsesecureclient
pulsesecuresteel belted radius

Check your server's TLS configuration

The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • openssl openssl1.0.1
  • openssl openssl1.0.1a
  • openssl openssl1.0.1b
  • openssl openssl1.0.1c
  • openssl openssl1.0.1d
  • openssl openssl1.0.1e
  • openssl openssl1.0.1f
  • openssl openssl1.0.1g

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12nssbefore 3.133.13
Debian:12opensslbefore 1.0.0c-21.0.0c-2
Red Hat:enterprise_linux:5::clientopensslbefore 0:0.9.8e-39.el5_110:0.9.8e-39.el5_11
Red Hat:enterprise_linux:5::clientopenssl-debuginfobefore 0:0.9.8e-39.el5_110:0.9.8e-39.el5_11
Red Hat:enterprise_linux:5::clientopenssl-perlbefore 0:0.9.8e-39.el5_110:0.9.8e-39.el5_11
Red Hat:enterprise_linux:5::client_workstationopenssl-develbefore 0:0.9.8e-39.el5_110:0.9.8e-39.el5_11
Red Hat:enterprise_linux:6::clientopensslbefore 0:1.0.1e-42.el6_7.40:1.0.1e-42.el6_7.4
Red Hat:enterprise_linux:6::clientopenssl-debuginfobefore 0:1.0.1e-42.el6_7.40:1.0.1e-42.el6_7.4
Red Hat:enterprise_linux:6::clientopenssl-develbefore 0:1.0.1e-42.el6_7.40:1.0.1e-42.el6_7.4
Red Hat:enterprise_linux:6::clientopenssl-perlbefore 0:1.0.1e-42.el6_7.40:1.0.1e-42.el6_7.4
Red Hat:enterprise_linux:6::clientopenssl-staticbefore 0:1.0.1e-42.el6_7.40:1.0.1e-42.el6_7.4
Red Hat:enterprise_linux:6::clientopenssl098ebefore 0:0.9.8e-20.el6_7.10:0.9.8e-20.el6_7.1
Red Hat:enterprise_linux:6::clientopenssl098e-debuginfobefore 0:0.9.8e-20.el6_7.10:0.9.8e-20.el6_7.1
Red Hat:enterprise_linux:6::hypervisorrhev-hypervisor7before 0:7.2-20160302.1.el6ev0:7.2-20160302.1.el6ev
Red Hat:enterprise_linux:7::clientopensslbefore 1:1.0.1e-51.el7_2.41:1.0.1e-51.el7_2.4
Red Hat:enterprise_linux:7::clientopenssl-debuginfobefore 1:1.0.1e-51.el7_2.41:1.0.1e-51.el7_2.4
Red Hat:enterprise_linux:7::clientopenssl-develbefore 1:1.0.1e-51.el7_2.41:1.0.1e-51.el7_2.4
Red Hat:enterprise_linux:7::clientopenssl-libsbefore 1:1.0.1e-51.el7_2.41:1.0.1e-51.el7_2.4
Red Hat:enterprise_linux:7::clientopenssl-perlbefore 1:1.0.1e-51.el7_2.41:1.0.1e-51.el7_2.4
Red Hat:enterprise_linux:7::clientopenssl-staticbefore 1:1.0.1e-51.el7_2.41:1.0.1e-51.el7_2.4
Red Hat:enterprise_linux:7::clientopenssl098ebefore 0:0.9.8e-29.el7_2.30:0.9.8e-29.el7_2.3
Red Hat:enterprise_linux:7::clientopenssl098e-debuginfobefore 0:0.9.8e-29.el7_2.30:0.9.8e-29.el7_2.3
Red Hat:enterprise_linux:7::hypervisorrhev-hypervisor7before 0:7.2-20160302.1.el7ev0:7.2-20160302.1.el7ev
Red Hat:rhel_aus:5.9opensslbefore 0:0.9.8e-26.el5_9.50:0.9.8e-26.el5_9.5

+50

Other highest-scoring records for the same primary product.

  • CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows…KEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This week
  • CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code…
    65This week

Published before and after this one in the same product

  • ← EarlierCVE-2015-3197Feb 14, 2016 · ssl/s2_srvr.c in OpenSSL 1.0.1 before 1.0.1r and 1.0.2 before 1.0.2f does not prevent use of disabled ciphers, which makes it easier for…
    26Monitor
  • ← EarlierCVE-2016-0701Feb 14, 2016 · The DH_check_pub_key function in crypto/dh/dh_check.c in OpenSSL 1.0.2 before 1.0.2f does not ensure that prime numbers are appropriate for…
    39Monitor
  • Later →CVE-2016-0703Mar 2, 2016 · The get_client_master_key function in s2_srvr.c in the SSLv2 implementation in OpenSSL before 0.9.8zf, 1.0.0 before 1.0.0r, 1.0.1 before…
    25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:nss3.13 · Debian:12Package registry (OSV)
debian:openssl1.0.0c-2 · Debian:12Package registry (OSV)
red hat:openssl0:1.0.1e-42.el6_7.4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:openssl-debuginfo0:1.0.1e-42.el6_7.4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:openssl-devel0:1.0.1e-42.el6_7.4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:openssl-libs1:1.0.1e-51.el7_2.4 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:openssl-perl0:1.0.1e-42.el6_7.4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:openssl-static0:1.0.1e-42.el6_7.4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:openssl098e0:0.9.8e-20.el6_7.1 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:openssl098e-debuginfo0:0.9.8e-20.el6_7.1 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:rhev-hypervisor70:7.2-20160302.1.el6ev · Red Hat:enterprise_linux:6::hypervisorPackage registry (OSV)
suse:compat-openssl097g0.9.7g-146.22.41.1 · SUSE:Linux Enterprise Desktop 11 SP4Package registry (OSV)
suse:compat-openssl0980.9.8j-94.1 · SUSE:Linux Enterprise Desktop 12Package registry (OSV)
suse:openssl1.0.1i-27.13.1 · SUSE:Linux Enterprise Desktop 12Package registry (OSV)
suse:openssl11.0.1g-0.40.1 · SUSE:Linux Enterprise Server 11-SECURITYPackage registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Metasploit moduleauxiliary/scanner/ssl/ssl_versionSSL/TLS Version Detectionauxiliary2014-10-14
Proof-of-concept repository on GitHubstars:52021-01-01

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Metasploit-505 d
  2. Published
  3. First PoC+1766 d
  4. TodayNov 15, 2026+3911 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

References

All records