Skip to content

containerd CRI stream server: Host memory exhaustion through Terminal resize goroutine leak

Moderate
samuelkarp published GHSA-2qjp-425j-52j9 Dec 7, 2022

Package

No package listed

Affected versions

< 1.5.16, 1.6.0-1.6.11

Patched versions

1.5.16, 1.6.12

Description

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:

Severity

Moderate

CVE ID

CVE-2022-23471

Weaknesses

No CWEs