GHSA-2qjp-425j-52j9

Source
https://github.com/advisories/GHSA-2qjp-425j-52j9
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/12/GHSA-2qjp-425j-52j9/GHSA-2qjp-425j-52j9.json
Aliases
Published
2022-12-07T23:23:43Z
Modified
2023-11-08T04:08:18.684282Z
Summary
containerd CRI stream server vulnerable to host memory exhaustion via terminal
Details

Impact

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.

Patches

This bug has been fixed in containerd 1.6.12 and 1.5.16. Users should update to these versions to resolve the issue.

Workarounds

Ensure that only trusted images and commands are used and that only trusted users have permissions to execute commands in running containers.

For more information

If you have any questions or comments about this advisory:

To report a security issue in containerd: * Report a new vulnerability * Email us at security@containerd.io

References

Affected packages

Go / github.com/containerd/containerd

Affected ranges

Type
SEMVER
Events
Introduced
0The exact introduced commit is unknown
Fixed
1.5.16

Go / github.com/containerd/containerd

Affected ranges

Type
SEMVER
Events
Introduced
1.6.0
Fixed
1.6.12