containerd image-triggered runtime DoS via unbounded group parsing
containerd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd/v2 Go |
|
|
containerd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd/v2 Go |
|
|
| github.com/containerd/containerd Go |
|
|
containerd is an open-source container runtime. Versions prior to 1.7.33, 2.0.10, 2.1.9, 2.2.5 and 2.3.2, contain a vulnerability that allows a maliciously crafted image to cause a Denial of Service (DoS) condition. When creating a container from this image, memory exhaustion occurs, leading to an Out Of Memory (OOM) kill of the containerd process. This renders the container runtime API unavailable and can disrupt clients such as the Docker Engine or Kubernetes control-plane components. This issue has been fixed in versions 1.7.33, 2.0.10, 2.1.9, 2.2.5 and 2.3.2.
From the CVE record · GitHub_M
Affected containerd versions can exhaust memory when creating a container from a maliciously crafted image. The resulting out-of-memory kill makes the container runtime API unavailable and can disrupt clients. The input does not specify network access or authentication requirements; the trigger is creating a container from the image.
Check deployments running containerd 1.7.0–1.7.32, 2.0.0–2.0.9, 2.1.0–2.1.8, 2.2.0–2.2.4, or 2.3.0–2.3.1.