containerd: CRI checkpoint import allows local image tag poisoning
containerd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd/v2 Go |
|
|
| github.com/containerd/containerd Go |
containerd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd/v2 Go |
|
|
| github.com/containerd/containerd Go |
all versions| No fix yet |
containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the CRI checkpoint import process where it fails to validate the image references specified within a checkpoint image's configuration. An attacker with permissions to create pods can use a crafted checkpoint image to force containerd to pull a malicious image and assign it an arbitrary local tag, thereby poisoning the node's local image cache. Subsequently, if other pods on the same node attempt to use the poisoned tag with an IfNotPresent (or Never) pull policy, they will unknowingly execute the attacker's malicious image instead of the legitimate one. This can lead to a compromise of the affected pods, allowing the attacker to execute arbitrary code under the victim pod's identity. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.
From the CVE record · GitHub_M
The CRI checkpoint import process fails to validate image references in a checkpoint image. An attacker with permission to create pods can import a crafted checkpoint that poisons a node’s local image cache; other pods on that node using the poisoned tag with an IfNotPresent or Never pull policy may then run the attacker’s image under their own identity.
Check deployments using Go package github.com/containerd/containerd/v2 versions >=2.1.0 <2.1.9, >=2.2.0 <2.2.5 or >=2.3.0 <2.3.2, or github.com/containerd/containerd at any version.