Default inheritable capabilities for linux container should be empty
Résumé
Default inheritable capabilities for linux container should be empty
Description d'origine
La description telle que publiée par la source (souvent en anglais).
Impact
A bug was found in runc where runc exec --cap executed processes with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2).
This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set.
Patches
This bug has been fixed in runc 1.1.2. Users should update to this version as soon as possible.
This fix changes runc exec --cap behavior such that the additional capabilities granted to the process being executed (as specified via --cap arguments) do not include inheritable capabilities.
In addition, runc spec is changed to not set any inheritable capabilities in the created example OCI spec (config.json) file.
Credits
The opencontainers project would like to thank Andrew G. Morgan for responsibly disclosing this issue in accordance with the opencontainers org security policy.
For more information
If you have any questions or comments about this advisory:
- Open an issue
- Email us at security@opencontainers.org if you think you’ve found a security bug
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Paquets affectés
État des correctifs par distribution
Paquets corrigés publiés par chaque distribution pour cette CVE
- Debian DEBIAN-CVE-2022-29162 runc Corrigé dans: 1.0.0~rc93+ds1-5+deb11u2
Références
- advisory nvd.nist.gov
- package github.com/opencontainers/runc
- web github.com
- web github.com
- web github.com
- web lists.debian.org
- web lists.fedoraproject.org
- web lists.fedoraproject.org
- web lists.fedoraproject.org