Skip to content
Fencer Intel
high 7.6

CVE-2013-4559 in the critical feed json

lighttpd before 1.4.33 does not check the return value of the (1) setuid, (2) setgid, or (3) setgroups functions, which might cause lighttp…

published 12y ago modified 4mo ago also EUVD-2013-4418

cvss
7.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.7%
EPSS 10.7% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

lighttpd before 1.4.33 does not check the return value of the (1) setuid, (2) setgid, or (3) setgroups functions, which might cause lighttpd to run as root if it is restarted and allows remote attackers to gain privileges, as demonstrated by multiple calls to the clone function that cause setuid to fail when the user process limit is reached.

Patch / fix

  • lighttpd lighttpd 1.4.33
  • lighttpd Debian 14, Debian 13, Debian 12 1.4.33-1+nmu1

debian advisories DEBIAN-CVE-2013-4559

  • lighttpd openSUSE Tumbleweed 1.4.37-1.6

opensuse advisories openSUSE-SU-2024:10402-1

Is CVE-2013-4559 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-2013-4559 updated cvss 4.6

lighttpd: setuid/setgid/setgroups return value check

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

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

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

CVSS scores

assigned by version score vector
NVD 2.0 7.6 AV:N/AC:H/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

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.