containerd has an integer overflow in User ID handling
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 |
|
|
containerd is an open-source container runtime. A bug was found in containerd prior to versions 1.6.38, 1.7.27, and 2.0.4 where containers launched with a User set as a `UID:GID` larger than the maximum 32-bit signed integer can cause an overflow condition where the container ultimately runs as root (UID 0). This could cause unexpected behavior for environments that require containers to run as a non-root user. This bug has been fixed in containerd 1.6.38, 1.7.27, and 2.04. As a workaround, ensure that only trusted images are used and that only trusted users have permissions to import images.
From the CVE record · GitHub_M
Affected containerd versions can overflow when a container is launched with a User UID:GID larger than the maximum 32-bit signed integer. The container can then run as root instead of the intended non-root user. The input does not specify network access, authentication requirements, or user interaction.
Teams running containerd before 1.6.38, from 1.7.0-beta.0 through versions before 1.7.27, or containerd/v2 before 2.0.4 should check their deployments.