containerd CRI server: Host memory exhaustion through Attach goroutine leak
- 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.29, 2.0.7, 2.1.5, 2.2.0
- 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. Versions 1.7.28 and below, 2.0.0-beta.0 through 2.0.6, 2.1.0-beta.0 through 2.1.4, and 2.2.0-beta.0 through 2.2.0-rc.1 contain a bug in the CRI Attach implementation where a user can exhaust memory on the host due to goroutine leaks. This issue is fixed in versions 1.7.29, 2.0.7, 2.1.5 and 2.2.0. To workaround this vulnerability, users can set up an admission controller to control accesses to pods/attach resources.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- containerd containerd
fixed in 1.7.29; fixed in 2.0.7; From 2.1.0-beta.0 · fixed in 2.1.5; From 2.2.0-beta.0 · fixed in 2.2.0
- github.com/containerd/containerdGo
fixed in 1.7.29
- github.com/containerd/containerd/v2Go
fixed in 2.0.7
- github.com/containerd/containerd/v2Go
From 2.1.0-beta.0 · fixed in 2.1.5
- github.com/containerd/containerd/v2Go
From 2.2.0-beta.0 · fixed in 2.2.0
- github.com/containerd/containerd/v2Go
fixed in 2.0.7; From 2.1.0-beta.0 · fixed in 2.1.5; From 2.2.0-beta.0 · fixed in 2.2.0