CVE-2016-2217 json
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 a…
published 2017-01-30 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-3301
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- socat Debian 14, Debian 13, Debian 12 1.7.3.1-1
debian advisories DEBIAN-CVE-2016-2217
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2016-2217 updated cvss 4.3
socat: Hard coded 1024 bit DH p parameter was not prime
-
Red Hat Enterprise Linux 7 socat Red Hat OpenShift Enterprise 2 socatnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.53% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-320 Key Management Errors
References
-
dest-unreach.org
/socat/contrib/socat-secadv7.html
patch, third-party-advisory
-
openwall.com
/lists/oss-security/2016/02/01/4
mailing-list, patch, third-party-advisory
-
security.gentoo.org
/glsa/201612-23
vendor-advisory
-
openwall.com
/lists/oss-security/2016/02/04/1
mailing-list, third-party-advisory
Sources
- CVE List CVE-2016-2217
- NVD CVE-2016-2217
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.