containerd is vulnerable to privilege escalation. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges.
github.com/advisories/GHSA-36xw-fx78-c5r4
github.com/containerd/containerd/commit/4a4bb851f5da563ff6e68a83dc837c7699c469ad
github.com/containerd/containerd/releases/tag/v1.4.3
github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4
lists.fedoraproject.org/archives/list/[email protected]/message/LNKXLOLZWO5FMAPX63ZL7JNKTNNT5NQD/
secdb.alpinelinux.org/v3.11/community.yaml
secdb.alpinelinux.org/v3.12/community.yaml
security.gentoo.org/glsa/202105-33
www.debian.org/security/2021/dsa-4865