Skip to content
Fencer Intel
high 7.5

CVE-2015-1379 json

The signal handler implementations in socat before 1.7.3.0 and 2.0.0-b8 allow remote attackers to cause a denial of service (process freeze…

published 9y ago modified 4mo ago also EUVD-2015-1516

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.9%
EPSS 3.9% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

The signal handler implementations in socat before 1.7.3.0 and 2.0.0-b8 allow remote attackers to cause a denial of service (process freeze or crash).

Patch / fix

  • socat Debian 14, Debian 13, Debian 12 1.7.2.4-2

debian advisories DEBIAN-CVE-2015-1379

  • socat Ubuntu Pro 14.04 LTS 1.7.2.3-1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2015-1379

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • socat SLES LTSS Extended Security 12 SP5 1.7.2.4-4.6.1

suse advisories SUSE-SU-2025:0726-1

Is CVE-2015-1379 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-1379 updated cvss 2.1

socat: possible DoS with fork

  • Red Hat Enterprise Linux 7 socat Red Hat OpenShift Enterprise 2 socat
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.93% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.