Name | CVE-2016-2217 |
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. |
Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Debian Bugs | 813536 |
Vulnerable and fixed packages
The table below lists information on source packages.
Source Package | Release | Version | Status |
---|
socat (PTS) | bullseye | 1.7.4.1-3 | fixed |
| bookworm | 1.7.4.4-2 | fixed |
| sid, trixie | 1.8.0.1-2 | fixed |
The information below is based on the following data on fixed versions.
Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
---|
socat | source | squeeze | (not affected) | | | |
socat | source | wheezy | (not affected) | | | |
socat | source | jessie | (not affected) | | | |
socat | source | (unstable) | 1.7.3.1-1 | | | 813536 |
Notes
[jessie] - socat <not-affected> (Broken 1024bit DH parameter generated in 1.7.3.0)
[wheezy] - socat <not-affected> (Broken 1024bit DH parameter generated in 1.7.3.0)
[squeeze] - socat <not-affected> (Broken 1024bit DH parameter generated in 1.7.3.0)
The issues is about "In the OpenSSL address implementation the hard coded 1024 bit DH
p parameter was not prime.". Upstream has generated new parametes (and made it 2048
bit long.
https://www.openwall.com/lists/oss-security/2016/02/01/4
http://www.dest-unreach.org/socat/contrib/socat-secadv7.html