Skip to content
Fencer Intel
medium 4.6

CVE-2011-4099 json

The capsh program in libcap before 2.22 does not change the current working directory when the --chroot option is specified, which allows l…

published 2014-02-08 12 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4050

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

Summary

The capsh program in libcap before 2.22 does not change the current working directory when the --chroot option is specified, which allows local users to bypass the chroot restrictions via unspecified vectors.

Patch / fix

  • libcap2 Debian 14, Debian 13, Debian 12 1:2.22-1

debian advisories DEBIAN-CVE-2011-4099

  • libcap RHEL 6 2.16-5.5.el6

red hat advisories RHSA-2011:1694

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-2011-4099 updated cvss 4.1

capsh: does not chdir after chroot

  • Red Hat Enterprise Linux Desktop (v. 6) libcap 2.16-5.5.el6 Red Hat Enterprise Linux Desktop Optional (v. 6) libcap 2.16-5.5.el6 Red Hat Enterprise Linux HPC Node (v. 6) libcap 2.16-5.5.el6 Red Hat Enterprise Linux HPC Node Optional (v. 6) libcap 2.16-5.5.el6 Red Hat Enterprise Linux Server (v. 6) libcap 2.16-5.5.el6 Red Hat Enterprise Linux Workstation (v. 6) libcap 2.16-5.5.el6
    fixed: vendor fix RHSA-2011:1694

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

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

CVSS scores

assigned by version score vector
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

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.