Ssst0N3

**Name of the Vulnerable Software and Affected Versions** containerd versions prior to 2.3.1 containerd versions prior to 2.2.4 containerd versions prior to 2.0.9 containerd versions prior to 1.7.32 **Description** An input validation error exists 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 includes an `/etc/passwd` file that maps this large numeric string to root, the container runs as root (UID 0). This allows the Kubernetes `runAsNonRoot` restriction to be bypassed, affecting environments that require containers to run as a non-root user. **Recommendations** Update to version 2.3.1. Update to version 2.2.4. Update to version 2.0.9. Update to version 1.7.32. Ensure only trusted images are used and only trusted users have permissions to import images. Enforce a specific numeric `runAsUser` in the Kubernetes Pod `securityContext` to override the `USER` directive in the image.

**Name of the Vulnerable Software and Affected Versions** runc versions prior to 1.1.5 **Description** The issue is related to the incorrect handling of symbolic links before accessing a file, which allows an attacker to access confidential data, compromise its integrity, and cause a denial of service. It was found that AppArmor can be bypassed when `/proc` inside the container is symlinked with a specific mount configuration. **Recommendations** For versions prior to 1.1.5, upgrade to version 1.1.5 or later to fix the issue. As a temporary workaround, consider avoiding the use of untrusted container images until the issue is resolved. Restrict access to the `/proc` endpoint inside the container to minimize the risk of exploitation.