Memory Leak Affecting containerd package, versions <1.4.13~ds1-1~deb11u3
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-DEBIAN11-CONTAINERD-3164767
- published 8 Dec 2022
- disclosed 7 Dec 2022
Introduced: 7 Dec 2022
CVE-2022-23471 Open this link in a new tabHow to fix?
Upgrade Debian:11 containerd to version 1.4.13ds1-1deb11u3 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream containerd package and not the containerd package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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.