Containerd has image-pull DoS via crafted OCI index graph amplification
- 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 2.0.13, 1.7.36, 2.2.9, 2.3.6, 2.4.1
- 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: yes
- Technical impact: partial
Summary
containerd is an open-source container runtime. Prior to versions 1.7.36, 2.0.13, 2.2.9, 2.3.6, and 2.4.1, a crafted OCI index graph can force very high CPU/memory usage during PullImage (before container start), causing long ContainerCreating stalls and, at larger sizes, node/runtime instability. Versions 1.7.36, 2.0.13, 2.2.9, 2.3.6, and 2.4.1 fix the issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- containerd containerd
From 2.0.0 · fixed in 2.0.13; fixed in 1.7.36; From 2.1.0 · fixed in 2.2.9; From 2.3.0 · fixed in 2.3.6
- github.com/containerd/containerd/v2Go
From 2.0.0 · fixed in 2.0.13
- github.com/containerd/containerdGo
fixed in 1.7.36
- github.com/containerd/containerd/v2Go
From 2.1.0 · fixed in 2.2.9
- github.com/containerd/containerd/v2Go
From 2.3.0 · fixed in 2.3.6
- github.com/containerd/containerd/v2Go
From 2.4.0 · fixed in 2.4.1
- github.com/containerd/containerd/v2Go
From 2.0.0 · fixed in 2.0.13; From 2.1.0 · fixed in 2.2.9; From 2.3.0 · fixed in 2.3.6; From 2.4.0 · fixed in 2.4.1