# CVE-2016-0800: Weak cryptography in n/a

> Remote attackers can decrypt TLS ciphertext data by exploiting the SSLv2 protocol's Bleichenbacher RSA padding oracle vulnerability in OpenSSL.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Mar 2016
- **Updated:** 5 Aug 2024
- **Also known as:** CVE-2016-8000, DEBIAN-CVE-2016-0800, GHSA-fqw2-3v24-gc79

## What is CVE-2016-0800?

CVE-2016-0800 is a medium-severity vulnerability in Openssl Openssl, published on 1 Mar 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-310, CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-0800?

It affects 3 products.


Products: Openssl Openssl, Pulsesecure Client, Pulsesecure Steel Belted Radius.

## How do I fix CVE-2016-0800?

Upgrade to a fixed version.

## Is CVE-2016-0800 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-0800 exists.

Public exploit code:

- A2SV = Auto Scanning to SSL Vulnerability HeartBleed, CCS Injection, SSLv3 POODLE, FREAK... etc Support Vulnerability [CVE-2007-1858] Anonymous Cipher [CVE-2012-4929] CRIME(SPDY) [CVE-2014-0160] CCS Injection [CVE-2014-0224] HeartBleed [CVE-2014-3566] SSLv3 POODLE [CVE-2015-0204] FREAK Attack [CVE-2015-4000] LOGJAM Attack [CVE-2016-0800] SSLv2 DROWN Installation : $ apt update && apt upgrade $ apt install git $ apt install python2 $ apt install python $ git clone https://github.com/hahwul/ a2sv $ cd a2sv $ chmod +x * $ pip2 install -r requirements.txt usage : $ python2 a2sv.py -h It shows all commands how we can use this tool $ python a2sv.py -t 127.0.0.1 127.0.0.1 = target means here own device (github_poc): https://github.com/anthophilee/A2SV--SSL-VUL-Scan
- SSL/TLS Version Detection (metasploit)

## Other vulnerabilities in Openssl Openssl

- [CVE-2009-3245](https://insights.sbomify.com/CVE-2009-3245/): Null dereference in n/a (critical 10.0)
- [CVE-2006-3738](https://insights.sbomify.com/CVE-2006-3738/): Memory corruption in n/a (critical 10.0)
- [CVE-2026-63073](https://insights.sbomify.com/CVE-2026-63073/): Untrusted Sender DN Used as Format String in CMP Response Validation (critical 9.8)
- [CVE-2016-6309](https://insights.sbomify.com/CVE-2016-6309/): Use after free in n/a (critical 9.8)
- [CVE-2016-0799](https://insights.sbomify.com/CVE-2016-0799/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-0800 and fix it if it is affected.

What it is: CVE-2016-0800 is a medium-severity vulnerability in Openssl Openssl, published on 1 Mar 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-0800 exists.

Affected product: Openssl Openssl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-0800/ (Markdown: https://insights.sbomify.com/CVE-2016-0800/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-0800
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-0800
- OSV: https://osv.dev/vulnerability/CVE-2016-0800

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-0800/
Summaries are generated and may contain mistakes; the official description above is the record.