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 1.0.1m, and 1.0.2 before 1.0.2a accepts a nonzero CLIENT-MASTER-KEY CLEAR-KEY-LENGTH value for an arbitrary cipher, which allows man-in-the-middle attackers to determine the MASTER-KEY value and decrypt TLS ciphertext data by leveraging a Bleichenbacher RSA padding oracle, a related issue to CVE-2016-0800.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.9, indicating it can be exploited remotely over the network but requires specific conditions to be met without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), for affected systems. Impacting 1 product from openssl organizations running these solutions should prioritize assessment and patching.
First disclosed in 2016, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.
2016-03-02T11:59:00.113
2025-04-12T10:46:40.837
Deferred
CVSSv3.0: 5.9 (MEDIUM)
AV:N/AC:M/Au:N/C:P/I:N/A:N
8.6
2.9
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | openssl | openssl | ≤ 0.9.8ze | Yes |
| Application | openssl | openssl | 1.0.0 | Yes |
| Application | openssl | openssl | 1.0.0 | Yes |
| Application | openssl | openssl | 1.0.0 | Yes |
| Application | openssl | openssl | 1.0.0 | Yes |
| Application | openssl | openssl | 1.0.0 | Yes |
| Application | openssl | openssl | 1.0.0 | Yes |
| Application | openssl | openssl | 1.0.0a | Yes |
| Application | openssl | openssl | 1.0.0b | Yes |
| Application | openssl | openssl | 1.0.0c | Yes |
| Application | openssl | openssl | 1.0.0d | Yes |
| Application | openssl | openssl | 1.0.0e | Yes |
| Application | openssl | openssl | 1.0.0f | Yes |
| Application | openssl | openssl | 1.0.0g | Yes |
| Application | openssl | openssl | 1.0.0h | Yes |
| Application | openssl | openssl | 1.0.0i | Yes |
| Application | openssl | openssl | 1.0.0j | Yes |
| Application | openssl | openssl | 1.0.0k | Yes |
| Application | openssl | openssl | 1.0.0l | Yes |
| Application | openssl | openssl | 1.0.0m | Yes |
| Application | openssl | openssl | 1.0.0n | Yes |
| Application | openssl | openssl | 1.0.0o | Yes |
| Application | openssl | openssl | 1.0.0p | Yes |
| Application | openssl | openssl | 1.0.0q | Yes |
| Application | openssl | openssl | 1.0.1 | Yes |
| Application | openssl | openssl | 1.0.1 | Yes |
| Application | openssl | openssl | 1.0.1 | Yes |
| Application | openssl | openssl | 1.0.1 | Yes |
| Application | openssl | openssl | 1.0.1a | Yes |
| Application | openssl | openssl | 1.0.1b | Yes |
| Application | openssl | openssl | 1.0.1c | Yes |
| Application | openssl | openssl | 1.0.1d | Yes |
| Application | openssl | openssl | 1.0.1e | Yes |
| Application | openssl | openssl | 1.0.1f | Yes |
| Application | openssl | openssl | 1.0.1g | Yes |
| Application | openssl | openssl | 1.0.1h | Yes |
| Application | openssl | openssl | 1.0.1i | Yes |
| Application | openssl | openssl | 1.0.1j | Yes |
| Application | openssl | openssl | 1.0.1k | Yes |
| Application | openssl | openssl | 1.0.1l | Yes |
| Application | openssl | openssl | 1.0.2 | Yes |
| Application | openssl | openssl | 1.0.2 | Yes |
| Application | openssl | openssl | 1.0.2 | Yes |
| Application | openssl | openssl | 1.0.2 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For openssl's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.