containerd CRI plugin: Host memory exhaustion through ExecSync
- 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.5.13, 1.6.6
- 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
Summary
containerd is an open source container runtime. A bug was found in the containerd's CRI implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the `ExecSync` API. This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to use containerd's CRI implementation; `ExecSync` may be used when running probes or when executing processes via an "exec" facility. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted images and commands are used.
Timeline
- CVE published
- Record last updated
Affected versions
- containerd containerd
fixed in 1.5.13; From 1.6.0 · fixed in 1.6.6
- github.com/containerd/containerdGo
fixed in 1.5.13; From 1.6.0 · fixed in 1.6.6
- github.com/containerd/containerdGo
fixed in 1.5.13
- github.com/containerd/containerdGo
From 1.6.0 · fixed in 1.6.6