Memory Leak Affecting ctop package, versions <0.7.7-r13
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-WOLFILATEST-CTOP-6597061
- published 11 Apr 2024
- disclosed 7 Dec 2022
Introduced: 7 Dec 2022
CVE-2022-23471 Open this link in a new tabHow to fix?
Upgrade Wolfi ctop to version 0.7.7-r13 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream ctop package and not the ctop package as distributed by Wolfi.
See How to fix? for Wolfi 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.