In-container privilege gain via inherited capabilities
Published Apr 18, 2022 · Updated Aug 3, 2024
Incorrect default permissions in CRI-O before 1.24.0 allow local users to gain additional capabilities inside a launched container. CRI-O initialized container processes with a nonempty inheritable capability set, so execve(2) promoted matching file capabilities into the permitted set. Exploitation requires control of a launched image containing an executable with inheritable file capabilities, and gained privileges remain within the container's capability bounding set.
Summary
What happened
Incorrect default permissions in CRI-O before 1.24.0 allow local users to gain additional capabilities inside a launched container. CRI-O initialized container processes with a nonempty inheritable capability set, so execve(2) promoted matching file capabilities into the permitted set. Exploitation requires control of a launched image containing an executable with inheritable file capabilities, and gained privileges remain within the container's capability bounding set.
The record
- CVE
- CVE-2022-27652
- Published
- Apr 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- CRI-O
- Product
- CRI-O
- Classifications
- CWE-276, T1610
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 18, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=Affects all versions.
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.
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