containerd has an integer overflow in User ID handling
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.6.38, 1.7.27, 2.0.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- containerd containerd
fixed in 1.6.38; From 1.7.0-beta.0 · fixed in 1.7.27; From 2.0.0-beta.0 · fixed in 2.0.4
- github.com/containerd/containerdGo
fixed in 1.6.38; From 1.7.0-beta.0 · fixed in 1.7.27
- github.com/containerd/containerd/v2Go
fixed in 2.0.4
- github.com/containerd/containerdGo
From 1.7.0-beta.0 · fixed in 1.7.27
- github.com/containerd/containerdGo
fixed in 1.6.38