| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/containerd/containerd | ≥ 1.7.27, < 1.7.32 | 1.7.32 |
| github.com/containerd/containerd/v2 | ≥ 2.0.4, < 2.0.9≥ 2.1.0-beta.0, < 2.2.4≥ 2.3.0-beta.0, < 2.3.1 | 2.0.92.2.42.3.1 |
| containerd | ≥ 1.7.27, < 1.7.32≥ 2.0.4, < 2.0.9≥ 2.1.0, < 2.2.4≥ 2.3.0, < 2.3.1 | 1.7.322.0.92.2.42.3.1 |
A bug was found in containerd where containers launched with a numeric User directive that cannot be parsed as a 32-bit integer are incorrectly treated as a username. If a crafted image provides an /etc/passwd file mapping this large numeric string to root, the container ultimately runs as root (UID 0). This allows the Kubernetes runAsNonRoot restriction to be bypassed, causing unexpected behavior for environments that require containers to run as a non-root user.
This bug has been fixed in the following containerd versions:
Note: The containerd 2.1 release has reached its end of life and a fixed version is not provided.
Users should update to these versions to resolve the issue.
Ensure that only trusted images are used and that only trusted users have permissions to import images. Alternatively, enforcing a specific numeric runAsUser in the Kubernetes Pod securityContext overrides the USER directive in the image and prevents the bypass. Newer versions of Kubernetes, starting with 1.34, also appear to enforce runAsNonRoot properly regardless of this bug.
The containerd project would like to thank Lei Wang (@ssst0n3) for responsibly disclosing this issue in accordance with the containerd security policy.
If there are any questions or comments about this advisory:
To report a security issue in containerd:
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free