CVE-2016-2217

NameCVE-2016-2217
DescriptionThe 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.
SourceCVE (at NVD; CERT, LWN, oss-sec, fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, Mageia, GitHub code/issues, web search, more)
NVD severitymedium
Debian Bugs813536

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
socat (PTS)jessie1.7.2.4-2fixed
stretch1.7.3.1-2+deb9u1fixed
buster1.7.3.2-2fixed
bullseye, sid1.7.3.4-1fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
socatsource(unstable)1.7.3.1-1813536
socatsourcejessie(not affected)
socatsourcesqueeze(not affected)
socatsourcewheezy(not affected)

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.
http://www.openwall.com/lists/oss-security/2016/02/01/4
http://www.dest-unreach.org/socat/contrib/socat-secadv7.html

Search for package or bug name: Reporting problems