CVE-2013-3571: 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

Routine

LOW 2.6DOWNGRADE

CVE-2013-3571 is a low-severity flaw (CVSS 2.6) affecting socat. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 option is enabled, allows remote attackers to cause a denial of service (file descriptor consumption) via multiple request that are refused based on the (1) sourceport, (2) lowport, (3) range, or (4) tcpwrap restrictions.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	2.6 (Low)
EPSS exploit chance	2.1% (top 19%)
CISA exploited list	No
Published	2014-05-08
Last modified	2026-06-16

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

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

Am I affected?

Timeline

2014-05-08 14:29 UTCPublished CVE record published
2026-06-16 23:55 UTCUpdated Record last modified

dest-unreach socat DOWNGRADE

Affected: 1.2.0.0 · 1.3.0.0 · 1.3.0.1 · 1.3.1.0 · 1.3.2.0 · 1.3.2.1 · 1.3.2.2 · 1.4.0.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.2.0.0

1. Check installed version

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

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

apt-cache madison socat sudo apt install socat=<VERSION_BEFORE_1.2.0.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.2.0.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-2013-3571?

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

Is CVE-2013-3571 being exploited?

CVE-2013-3571 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-2013-3571 affect?

CVE-2013-3571 affects socat. Severity is low (CVSS 2.6). 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 option is enabled, allows remote attackers to cause a denial of service (file descriptor consumption) via multiple request that are

How urgent is CVE-2013-3571?

Priority 29/100. No elevated risk signals yet.

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-2016-2217 MEDIUM 5.3 DOWNGRADE 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
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-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