containerd: Unpack DoS via repeated opaque whiteouts
containerd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd/v2 Go |
|
|
| github.com/containerd/containerd Go |
containerd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd/v2 Go |
|
|
| github.com/containerd/containerd Go |
< 1.7.35
|
containerd is an open-source container runtime. Prior to 1.7.35, 2.0.12, 2.2.8, and 2.3.5, containerd's layer unpack handler repeatedly traverses directories for certain opaque whiteout configurations. A malicious image layer can trigger repeated directory traversals while opaque whiteouts are processed. Pulling or importing the image can consume CPU, delay container startup, and reduce image-pull concurrency for unrelated deployments. This issue is fixed in versions 1.7.35, 2.0.12, 2.2.8, and 2.3.5.
From the CVE record · GitHub_M
containerd's layer unpack handler repeatedly traverses directories when processing certain opaque whiteouts in a malicious image layer. Pulling or importing that image can consume CPU, delay container startup, and reduce image-pull concurrency for unrelated deployments.
Operators using containerd versions before 1.7.35 or 2.0.12, or versions 2.2.0–2.2.7 or 2.3.0–2.3.4, should check their installations.