| Version | Supported |
|---|---|
| 1.0.x | Yes |
If you discover a security vulnerability in Compartment, please report it responsibly:
- Email: nenad@micic.be
- Subject:
[SECURITY] compartment: <brief description> - Include: steps to reproduce, affected version, potential impact
Please do not open a public GitHub issue for security vulnerabilities.
- Acknowledgment within 72 hours
- Fix or mitigation within 30 days for confirmed vulnerabilities
- Credit in release notes (unless you prefer anonymity)
In scope:
- Sandbox escapes (Landlock, seccomp, namespace bypasses)
- Privilege escalation via compartment-user or compartment-root
- Environment variable injection past the sanitize filter
- Profile parsing bugs that weaken the intended policy
- Shell-replacement mode bypasses
Out of scope:
- Bugs in the Linux kernel itself (report to kernel security team)
- Attacks requiring pre-existing root access on the host
- Denial of service against the sandboxed process (not a goal)
See the README disclaimer and DESIGN.md for documented limitations, including:
- No formal verification or professional penetration testing
- Network egress bypass testing not yet automated for sandbox.sh HARD mode
- compartment-root not tested under actual root (test suite runs rootless)