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.
Published 2022-12-07 23:15:10
Updated 2024-01-31 13:15:09
Source GitHub, Inc.
View at NVD,

Exploit prediction scoring system (EPSS) score for CVE-2022-23471

Probability of exploitation activity in the next 30 days EPSS Score History
~ 32 %
Percentile, the proportion of vulnerabilities that are scored at or less

CVSS scores for CVE-2022-23471

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
GitHub, Inc.

CWE ids for CVE-2022-23471

  • The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.
    Assigned by: (Secondary)
  • The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.
    Assigned by: (Primary)

References for CVE-2022-23471

Products affected by CVE-2022-23471

This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to terms of use!