containerd: Arbitrary host CRI log file read via symlink following in CRI checkpoint restore
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 bug where the CRI plugin restores container.log from a checkpoint image without validating a symlinked path. This could result in reading an arbitrary file on the host via kubectl logs. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.
From the CVE record · GitHub_M
The containerd CRI plugin restores container.log from a checkpoint image without validating a symlinked path. If a checkpoint contains such a path, an attacker could read an arbitrary host file via kubectl logs. The input does not specify authentication requirements.
Engineers running containerd with 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, should check their deployments.