CVE-2016-2217

Name: CVE-2016-2217
Creator: NVD / NIST
Published: 2017-01-30T22:59:00.31+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 2.53%

Last modified Jun 17, 2026

CVE-2016-2217 is a vulnerability of currently unknown severity. The OpenSSL address implementation in Socat 1.7.3.0 and 2.0.0-b8 does not use a prime number for the DH, which makes it easier for remote attackers to obtain the shared secret.. EPSS estimates a 2.53% chance of exploitation in the next 30 days.

Description

The OpenSSL address implementation in Socat 1.7.3.0 and 2.0.0-b8 does not use a prime number for the DH, which makes it easier for remote attackers to obtain the shared secret.

Metrics

EPSS Probability

2.53%

82.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-320

Affected Software

Vendor	Product	Versions	Update
Dest-Unreach	Socat	1.7.3.0	—
Dest-Unreach	Socat	2.0.0	B8

References

http://www.dest-unreach.org/socat/contrib/socat-secadv7.htmlPatch, Third Party Advisory
http://www.openwall.com/lists/oss-security/2016/02/01/4Mailing List, Patch, Third Party Advisory
http://www.openwall.com/lists/oss-security/2016/02/04/1Third Party Advisory
https://security.gentoo.org/glsa/201612-23
http://www.dest-unreach.org/socat/contrib/socat-secadv7.htmlPatch, Third Party Advisory
http://www.openwall.com/lists/oss-security/2016/02/01/4Mailing List, Patch, Third Party Advisory
http://www.openwall.com/lists/oss-security/2016/02/04/1Third Party Advisory
https://security.gentoo.org/glsa/201612-23

Timeline

Published: Jan 30, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2016-2217?

The OpenSSL address implementation in Socat 1.7.3.0 and 2.0.0-b8 does not use a prime number for the DH, which makes it easier for remote attackers to obtain the shared secret.

How severe is CVE-2016-2217?

Severity scoring for CVE-2016-2217 is pending analysis. The EPSS model estimates a 2.53% probability of exploitation in the next 30 days.

How do I fix CVE-2016-2217?

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-2217?

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

Scan your code now

Source: NVD / NIST