CVE-2022-23471: containerd CRI stream server: Host memory exhaustion through terminal resize goroutine leak

Published Dec 7, 2022
·
Updated

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:

Open an issue in containerd Email us at security@containerd.io

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

Other sources

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.

NVD

Affected Software

4 affected componentsFixes available
go/github.com/containerd/containerd>=1.6.0<1.6.12
1.6.12
go/github.com/containerd/containerd<1.5.16
1.5.16
linuxfoundation Containerd<1.5.16
linuxfoundation Containerd>=1.6.0<1.6.12

Event History

Dec 7, 2022
CVE Published
via MITRE·10:51 PM
Data Sourced
via MITRE·10:51 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·11:23 PM

Frequently Asked Questions

1

What is CVE-2022-23471?

CVE-2022-23471 is a vulnerability in containerd, an open source container runtime, that allows a user to exhaust memory on the host.

2

How does CVE-2022-23471 affect Linuxfoundation Containerd?

Linuxfoundation Containerd versions 1.5.16 and between 1.6.0 to 1.6.12 are affected by CVE-2022-23471.

3

What is the severity of CVE-2022-23471?

CVE-2022-23471 has a severity rating of 6.5 (medium).

4

How can I fix CVE-2022-23471?

To fix CVE-2022-23471, upgrade containerd to a version that is not affected by the vulnerability.

5

Is there any additional information about CVE-2022-23471?

More information about CVE-2022-23471 can be found in the GitHub references provided.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203