Advisory

GHSA-2qjp-425j-52j9

Also known as: CVE-2022-23471, GO-2022-1147

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:

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2022-12-07 23:23 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

github.com/containerd/containerd

Go · All systems

Affected

  • introduced 0, fixed 1.5.16 (semver)

Fixed versions

1.5.16

Fix

github.com/containerd/containerd

Go · All systems

Affected

  • introduced 1.6.0, fixed 1.6.12 (semver)

Fixed versions

1.6.12

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences