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

This month

MEDIUM 5.3REMOTEWATCHLISTDOWNGRADE

CVE-2016-2217 is a medium-severity flaw (CVSS 5.3) affecting socat. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Remotely exploitable, no login, no user action
On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.5% (top 15%)
CISA exploited list	No
Weakness	CWE-320
Published	2017-01-30
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: dest-unreach

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-01-30 22:59 UTCPublished CVE record published
2026-06-17 00:43 UTCUpdated Record last modified

dest-unreach socat DOWNGRADE

Affected: 1.7.3.0 · 2.0.0 b8

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.7.3.0

1. Check installed version

apt-cache policy socat || rpm -q socat || socat --version

2. No fixed release: DOWNGRADE to a release before 1.7.3.0 (Debian / Ubuntu)

apt-cache madison socat sudo apt install socat=<VERSION_BEFORE_1.7.3.0> sudo apt-mark hold socat

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list socat sudo dnf downgrade socat-<VERSION_BEFORE_1.7.3.0> sudo dnf versionlock add socat

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-2217?

socat: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2016-2217 being exploited?

CVE-2016-2217 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-2217 affect?

CVE-2016-2217 affects socat. Severity is medium (CVSS 5.3). 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 urgent is CVE-2016-2217?

Priority 50/100. Remotely exploitable, no login, no user action; On your watchlist

Software pages

OpenSSL vulnerabilities

Related CVEs

CVE-2026-56123 HIGH 8.1 UPGRADE socat versions 1.8.0.0 through 1.8.1.1 contain a heap-based buffer overflow vulnerability that allows a malici
CVE-2015-1379 HIGH 7.5 UPGRADE The signal handler implementations in socat before 1.7.3.0 and 2.0.0-b8 allow remote attackers to cause a deni
CVE-2014-0019 LOW 1.9 DOWNGRADE MITIGATE Stack-based buffer overflow in socat 1.3.0.0 through 1.7.2.2 and 2.0.0-b1 through 2.0.0-b6 allows local users
CVE-2013-3571 LOW 2.6 DOWNGRADE socat 1.2.0.0 before 1.7.2.2 and 2.0.0-b1 before 2.0.0-b6, when used for a listen type address and the fork op
CVE-2012-0219 MEDIUM 6.2 DOWNGRADE Heap-based buffer overflow in the xioscan_readline function in xio-readline.c in socat 1.4.0.0 through 1.7.2.0

References

← Back to latest CVEs