Resource exhaustion in Containerd
CVE-2022-23471
containerd is an open source container runtime. A bug was found in containerd's CRI implementation where a user can exhaust memory on the host. In the CRI stream server, a goroutine is launched to handle terminal resize events if a TTY is requested. If the user's process fails to launch due to, for example, a faulty command, the goroutine will be stuck waiting to send without a receiver, resulting in a memory leak. Kubernetes and crictl can both be configured to use containerd's CRI implementation and the stream server is used for handling container IO. This bug has been fixed in containerd 1.6.12 and 1.5.16. Users should update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted images and commands are used and that only trusted users have permissions to execute commands in running containers.
Vulnerability class: DoS (Denial of Service)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.7 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.011, 66.6th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Containerd — versions < 1.5.16, >= 1.6.0, < 1.6.12
- Linuxfoundation Containerd
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (8-cm/kube-dump, ARPSyndicate/cvemon). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- https://github.com/containerd/containerd/security/advisories/GHSA-2qjp-425j-52j9 (Third Party Advisory)
- https://github.com/containerd/containerd/commit/a05d175400b1145e5e6a735a6710579d181e7fb0 (Patch, Third Party Advisory)
- security.gentoo.org/glsa/202401-31