containerd CRI plugin: Checkpoint restore bypasses destination security context
containerd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd/v2 Go |
|
|
| github.com/containerd/containerd Go |
| No fix yet |
containerd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd/v2 Go |
|
|
| github.com/containerd/containerd Go |
| No fix yet |
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.
From the CVE record · GitHub_M
containerd’s CRI CreateContainer checkpoint restore can restore process security settings from checkpoint data instead of enforcing the destination container configuration. An attacker who can create a container from a crafted checkpoint can run the restored process as root with full capabilities and without enforced seccomp filters, even while CRI reports the requested configuration. Systems that do not use CRI checkpoint restore are not affected.
Operators using CRI checkpoint restore should check Go package github.com/containerd/containerd/v2 versions >=2.1.0 <2.2.7 or >=2.3.0 <2.3.4, and github.com/containerd/containerd, for which no fixed version is listed.