CVE-2022-23471

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account, but needs a user to act. High risk of service disruption.

Exploit odds

1.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2022-12-07 23:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 04:30 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.1% in the next 30 days (EPSS).
• Severity: 5.7 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2022-12-07 23:15 UTC

Last modified

2026-06-17 04:30 UTC

Exploit probability

1.1% · EPSS, next 30 days

Weakness

CWE-400 · Uncontrolled resource consumption

Record status

Modified

Affected

• Linuxfoundation Containerd < 1.5.16
• Linuxfoundation Containerd < 1.6.12

Attack profile CVSS 3.1 · 5.7

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-23471.md and follow it. Check whether this project is affected by CVE-2022-23471. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge