GHSA-m8cg-xc2p-r3fc

Source

https://github.com/advisories/GHSA-m8cg-xc2p-r3fc

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/03/GHSA-m8cg-xc2p-r3fc/GHSA-m8cg-xc2p-r3fc.json

Aliases

• CVE-2023-25809

Published

2023-03-30T20:17:24Z

Modified

2023-11-08T04:11:55.808079Z

Details

Impact

It was found that rootless runc makes /sys/fs/cgroup writable in following conditons: 1. when runc is executed inside the user namespace, and the config.json does not specify the cgroup namespace to be unshared (e.g.., (docker|podman|nerdctl) run --cgroupns=host, with Rootless Docker/Podman/nerdctl) 2. or, when runc is executed outside the user namespace, and /sys is mounted with rbind, ro (e.g., runc spec --rootless; this condition is very rare)

A container may gain the write access to user-owned cgroup hierarchy /sys/fs/cgroup/user.slice/... on the host . Other users's cgroup hierarchies are not affected.

Patches

v1.1.5 (planned)

Workarounds

• Condition 1: Unshare the cgroup namespace ((docker|podman|nerdctl) run --cgroupns=private). This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts.
• Condition 2 (very rare): add /sys/fs/cgroup to maskedPaths

References

• https://github.com/opencontainers/runc/security/advisories/GHSA-m8cg-xc2p-r3fc
• https://nvd.nist.gov/vuln/detail/CVE-2023-25809
• https://github.com/opencontainers/runc/commit/0d62b950e60f6980b54fe3bafd9a9c608dc1df17
• https://github.com/opencontainers/runc