containerd: Unpack DoS via repeated opaque whiteouts
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.7.35, 2.0.12, 2.2.8, 2.3.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- containerd containerd
fixed in 1.7.35; From 2.0.0-beta.0 · fixed in 2.0.12; From 2.2.0 · fixed in 2.2.8; From 2.3.0 · fixed in 2.3.5
- github.com/containerd/containerd/v2Go
fixed in 2.0.12
- github.com/containerd/containerdGo
fixed in 1.7.35
- github.com/containerd/containerd/v2Go
From 2.2.0 · fixed in 2.2.8
- github.com/containerd/containerd/v2Go
From 2.3.0 · fixed in 2.3.5
- github.com/containerd/containerd/v2Go
fixed in 2.0.12; From 2.2.0 · fixed in 2.2.8; From 2.3.0 · fixed in 2.3.5