Insecure handling of image volumes in containerd CRI plugin
26Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 27%
exploitation probability
27%top 2% of all CVEs
observed exploitation
nono source reports it
containerd is a container runtime available as a daemon for Linux and Windows. A bug was found in containerd prior to versions 1.6.1, 1.5.10, and 1.14.12 where containers launched through containerd’s CRI implementation on Linux with a specially-crafted image configuration could gain access to read-only copies of arbitrary files and directories on the host. This may bypass any policy-based enforcement on container setup (including a Kubernetes Pod Security Policy) and expose potentially sensitive information. Kubernetes and crictl can both be configured to use containerd’s CRI implementation. This bug has been fixed in containerd 1.6.1, 1.5.10, and 1.4.12. Users should update to these versions to resolve the issue.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected products
containerd · containerdReferences
http://packetstormsecurity.com/files/166421/containerd-Image-Volume-Insecure-Handling.htmlhttps://github.com/containerd/containerd/commit/10f428dac7cec44c864e1b830a4623af27a9fc70https://github.com/containerd/containerd/releases/tag/v1.4.13https://github.com/containerd/containerd/releases/tag/v1.5.10https://github.com/containerd/containerd/releases/tag/v1.6.1https://github.com/containerd/containerd/security/advisories/GHSA-crp2-qrr5-8pq7https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/AUDQUQBZJGBWJPMRVB6QCCCRF7O3O4PA/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HFTS2EF3S7HNYSNZSEJZIJHPRU7OPUV3/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OCCARJ6FU4MWBTXHZNMS7NELPDBIX2VO/https://security.gentoo.org/glsa/202401-31https://www.debian.org/security/2022/dsa-5091