CVE-2016-2217
published 2017-01-30CVE-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…
PriorityP426medium5.3CVSS 3.0
AVNACLPRNUINSUCLINAN
EPSS
2.53%
82.9th percentile
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.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | socat | < socat 1.7.3.1-1 (bookworm) | socat 1.7.3.1-1 (bookworm) |
| dest-unreach | socat | — | — |
| dest-unreach | socat | — | — |
| dest-unreach | socat | >= 0 < 1.7.3.1-1 | 1.7.3.1-1 |
| dest-unreach | socat | >= 0 < 1.7.3.1-1 | 1.7.3.1-1 |
| dest-unreach | socat | >= 0 < 1.7.3.1-1 | 1.7.3.1-1 |
| dest-unreach | socat | >= 0 < 1.7.3.1-1 | 1.7.3.1-1 |
CVSS provenance
nvdv3.05.3MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
osv5.3MEDIUM
vendor_debian5.3MEDIUM
vendor_redhat5.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-x8h2-j222-xxr3: The OpenSSL address implementation in Socat 1
ghsa_unreviewed·2022-05-17
CVE-2016-2217 [MEDIUM] GHSA-x8h2-j222-xxr3: The OpenSSL address implementation in Socat 1
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.
OSV
CVE-2016-2217: The OpenSSL address implementation in Socat 1
osv·2017-01-30·CVSS 5.3
CVE-2016-2217 [MEDIUM] CVE-2016-2217: The OpenSSL address implementation in Socat 1
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.
Red Hat
socat: Hard coded 1024 bit DH p parameter was not prime
vendor_redhat·2016-02-01·CVSS 5.3
CVE-2016-2217 [MEDIUM] CWE-327 socat: Hard coded 1024 bit DH p parameter was not prime
socat: Hard coded 1024 bit DH p parameter was not prime
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.
Package: socat (Red Hat Enterprise Linux 7) - Not affected
Package: socat (Red Hat OpenShift Enterprise 2) - Not affected
Debian
CVE-2016-2217: socat - The OpenSSL address implementation in Socat 1.7.3.0 and 2.0.0-b8 does not use a ...
vendor_debian·2016·CVSS 5.3
CVE-2016-2217 [MEDIUM] CVE-2016-2217: socat - The OpenSSL address implementation in Socat 1.7.3.0 and 2.0.0-b8 does not use a ...
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.
Scope: local
bookworm: resolved (fixed in 1.7.3.1-1)
bullseye: resolved (fixed in 1.7.3.1-1)
forky: resolved (fixed in 1.7.3.1-1)
sid: resolved (fixed in 1.7.3.1-1)
trixie: resolved (fixed in 1.7.3.1-1)
No detection rules found.
No public exploits indexed.
http://www.dest-unreach.org/socat/contrib/socat-secadv7.htmlhttp://www.openwall.com/lists/oss-security/2016/02/01/4http://www.openwall.com/lists/oss-security/2016/02/04/1https://security.gentoo.org/glsa/201612-23http://www.dest-unreach.org/socat/contrib/socat-secadv7.htmlhttp://www.openwall.com/lists/oss-security/2016/02/01/4http://www.openwall.com/lists/oss-security/2016/02/04/1https://security.gentoo.org/glsa/201612-23
2017-01-30
Published