Skip to content
Fencer Intel
high 7.8

CVE-2019-5164 json

An exploitable code execution vulnerability exists in the ss-manager binary of Shadowsocks-libev 3.3.2.

published 6y ago modified 4mo ago also EUVD-2019-14769

cvss
7.8
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

An exploitable code execution vulnerability exists in the ss-manager binary of Shadowsocks-libev 3.3.2. Specially crafted network packets sent to ss-manager can cause an arbitrary binary to run, resulting in code execution and privilege escalation. An attacker can send network packets to trigger this vulnerability.

Patch / fix

  • shadowsocks-libev Debian 13, Debian 12 3.3.3+ds-2

debian advisories DEBIAN-CVE-2019-5164

  • shadowsocks-libev openSUSE Tumbleweed 3.3.5-1.9
  • shadowsocks-libev Package Hub 15 SP1 3.3.3-bp151.5.3.1
  • shadowsocks-libev openSUSE Leap 15.1 3.3.3-lp151.2.3.1

opensuse advisories openSUSE-SU-2024:11379-1openSUSE-SU-2020:0142-1openSUSE-SU-2019:2667-1

Is CVE-2019-5164 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

Exploit prediction

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

Exploits and checks

  • talosintelligence.com https://talosintelligence.com/vulnerability_reports/TALOS-2019-0958 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • n/a Shadowsocks

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality

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.