containerd CRI plugin: Checkpoint restore bypasses destination security context
- 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.2.7, 2.3.4
- 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. From 2.1.0 until 2.2.7 and 2.3.4, containerd's CRI CreateContainer checkpoint restore is vulnerable because CRIU restores process security state from checkpoint data instead of enforcing the destination ContainerConfig. An attacker who can create a container from a crafted checkpoint can supply restored credentials, capabilities, no_new_privs, and seccomp state. The restored process can run as root with full capabilities and no enforced seccomp filters while CRI status reports the requested configuration. Systems that do not use CRI checkpoint restore are not affected. This issue is fixed in versions 2.2.7 and 2.3.4.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- containerd containerd
From 2.1.0 · fixed in 2.2.7; From 2.3.0 · fixed in 2.3.4
- github.com/containerd/containerd/v2Go
From 2.1.0 · fixed in 2.2.7
- github.com/containerd/containerd/v2Go
From 2.3.0 · fixed in 2.3.4
- github.com/containerd/containerdGo
All versions
- github.com/containerd/containerd/v2Go
From 2.1.0 · fixed in 2.2.7; From 2.3.0 · fixed in 2.3.4