CVE-2016-0701

What it is

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 Diffie-Hellman (DH) key exchange, which makes it easier for remote attackers to discover a private DH exponent by making multiple handshakes with a peer that chose an inappropriate number, as demonstrated by a number in an X9.42 file.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

83.6% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2016-02-15 02:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:38 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 83.6% in the next 30 days (EPSS).
• Severity: 3.7 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2016-02-15 02:59 UTC

Last modified

2026-06-17 00:38 UTC

Exploit probability

83.6% · EPSS, next 30 days

Weakness

CWE-200 · Information exposure

Record status

Modified

Affected

• OpenSSL 1.0.2
• OpenSSL 1.0.2a
• OpenSSL 1.0.2b
• OpenSSL 1.0.2c
• OpenSSL 1.0.2d
• OpenSSL 1.0.2e

Attack profile CVSS 3.0 · 3.7

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-0701.md and follow it. Check whether this project is affected by CVE-2016-0701. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge