containerd affected by a local privilege escalation via wide permissions on CRI directory
containerd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd Go |
|
|
| github.com/containerd/containerd/v2 Go |
|
containerd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd Go |
|
|
| github.com/containerd/containerd/v2 Go |
|
2.0.72.1.52.2.0containerd is an open-source container runtime. Versions 0.1.0 through 1.7.28, 2.0.0-beta.0 through 2.0.6, 2.1.0-beta.0 through 2.1.4 and 2.2.0-beta.0 through 2.2.0-rc.1 have an overly broad default permission vulnerability. Directory paths `/var/lib/containerd`, `/run/containerd/io.containerd.grpc.v1.cri` and `/run/containerd/io.containerd.sandbox.controller.v1.shim` were all created with incorrect permissions. This issue is fixed in versions 1.7.29, 2.0.7, 2.1.5 and 2.2.0. Workarounds include updating system administrator permissions so the host can manually chmod the directories to not have group or world accessible permissions, or to run containerd in rootless mode.
From the CVE record · GitHub_M
containerd creates several runtime directories with permissions that are too broad. Users with local access may be able to access these directories through group or world permissions; no user interaction is described.
Operators running affected containerd versions or the Go packages github.com/containerd/containerd and github.com/containerd/containerd/v2 should check their installations.