containerd CRI plugin: — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull
- 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.33, 2.0.10, 2.1.9, 2.2.5, 2.3.2
- 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: total
Summary
containerd is an open-source container runtime. In versions prior to 1.7.33, 2.3.2, 2.2.5, 2.1.9, and 2.0.10 the CRI plugin propagates labels from an image config (LABEL instruction in Dockerfile) to a container without validation. This may result in executing an arbitrary command on the host, via a plugin that consumes container labels for some operations. This issue has been fixed in versions 1.7.33, 2.3.2, 2.2.5, 2.1.9, and 2.0.10.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- containerd containerd
fixed in 1.7.33; From 2.0.0 · fixed in 2.0.10; From 2.1.0 · fixed in 2.1.9; From 2.2.0 · fixed in 2.2.5; From 2.3.0 · fixed in 2.3.2
- github.com/containerd/containerdGo
From 1.7.0 · fixed in 1.7.33
- github.com/containerd/containerd/v2Go
From 2.0.0 · fixed in 2.0.10; From 2.1.0 · fixed in 2.1.9; From 2.2.0 · fixed in 2.2.5; From 2.3.0 · fixed in 2.3.2
- github.com/containerd/containerd/v2Go
From 2.0.0 · fixed in 2.0.10
- github.com/containerd/containerd/v2Go
From 2.1.0 · fixed in 2.1.9
- github.com/containerd/containerd/v2Go
From 2.2.0 · fixed in 2.2.5
- github.com/containerd/containerd/v2Go
From 2.3.0 · fixed in 2.3.2