CVE-2022-23471
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.
Does this matter?
Lower severity and a low EPSS score (1.02%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.1
- 6.5 MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 1.02% probability · 61th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-400, CWE-401
- Affected
- linuxfoundation/containerd
- Source
- security-advisories@github.com
References
- https://github.com/containerd/containerd/commit/a05d175400b1145e5e6a735a6710579d181e7fb0Patch, Third Party Advisory
- https://github.com/containerd/containerd/security/advisories/GHSA-2qjp-425j-52j9Third Party Advisory
- https://security.gentoo.org/glsa/202401-31
- https://github.com/containerd/containerd/commit/a05d175400b1145e5e6a735a6710579d181e7fb0Patch, Third Party Advisory
- https://github.com/containerd/containerd/security/advisories/GHSA-2qjp-425j-52j9Third Party Advisory
- https://security.gentoo.org/glsa/202401-31
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.