Container-root execution via unchecked UID conversion
Published Mar 17, 2025 · Updated May 4, 2025
Integer overflow in containerd allows local users with image-import rights to run a crafted container as root inside it. The oci.WithUser option parses each numeric UID and GID as a native integer, then converts it to uint32 without enforcing runc's signed 32-bit limit. Import and container-launch permissions are required, and the consequence is root identity inside the container rather than host-root execution.
Summary
What happened
Integer overflow in containerd allows local users with image-import rights to run a crafted container as root inside it. The oci.WithUser option parses each numeric UID and GID as a native integer, then converts it to uint32 without enforcing runc's signed 32-bit limit. Import and container-launch permissions are required, and the consequence is root identity inside the container rather than host-root execution.
The record
- CVE
- CVE-2024-40635
- Published
- Mar 17, 2025
- Updated
- May 4, 2025
- Vendor
- containerd
- Product
- containerd
- Classifications
- CWE-190, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 17, 2025CVE publishedPublication date reported by the CVE source.
- May 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.6.38
- Affected versionversion=>= 1.7.0-beta.0, < 1.7.27
- Affected versionversion=>= 2.0.0-beta.0, < 2.0.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo