CVE-2011-4099
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.
Does this matter?
Lower severity and a low EPSS score (0.38%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 2.0
- 4.6 MEDIUMAV:L/AC:L/Au:N/C:P/I:P/A:P
- EPSS
- 0.38% probability · 32th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-264
- Affected
- libcap/libcap
- Source
- secalert@redhat.com
EPSS 0.4% since 26 October 2026; no change recorded yet. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
References
- http://rhn.redhat.com/errata/RHSA-2011-1694.html
- https://bugzilla.redhat.com/show_bug.cgi?id=722694Vendor Advisory
- https://sites.google.com/site/fullycapable/release-notes-for-libcap/releasenotesfor222
- http://rhn.redhat.com/errata/RHSA-2011-1694.html
- https://bugzilla.redhat.com/show_bug.cgi?id=722694Vendor Advisory
- https://sites.google.com/site/fullycapable/release-notes-for-libcap/releasenotesfor222
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.