Privilege escalation via inherited process capabilities
Published Apr 4, 2022 · Updated Aug 3, 2024
Incorrect default permissions in crun 1.4.3 and earlier allow attackers to gain additional Linux process capabilities through crun exec. crun exec copies its requested capability array into the new process's inheritable set instead of leaving that set empty, so execve promotes matching inheritable file capabilities into the permitted set. Exploitation requires access to a container executable with inheritable file capabilities; gained privileges remain within the container bounding set.
Summary
What happened
Incorrect default permissions in crun 1.4.3 and earlier allow attackers to gain additional Linux process capabilities through crun exec. crun exec copies its requested capability array into the new process's inheritable set instead of leaving that set empty, so execve promotes matching inheritable file capabilities into the permitted set. Exploitation requires access to a container executable with inheritable file capabilities; gained privileges remain within the container bounding set.
The record
- CVE
- CVE-2022-27650
- Published
- Apr 4, 2022
- Updated
- Aug 3, 2024
- Vendor
- Containers
- Product
- crun
- Classifications
- CWE-276, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 4, 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 crun v1.4.3 and prior, Fixed in – v1.4.4
What conditions does exploitation require?
What is affected?
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