File access-control bypass via omitted primary group
Published Sep 19, 2022 · Updated May 29, 2025
Improper access control in CRI-O before 1.25.0 allows local users in a container to read or modify protected files. CRI-O omits the container user’s primary GID from AdditionalGids, so a set-group binary can drop that group and bypass negative group permissions. Exploitation requires code execution in an affected Linux container and files whose group permission bits deny more access than their other bits.
Summary
What happened
Improper access control in CRI-O before 1.25.0 allows local users in a container to read or modify protected files. CRI-O omits the container user’s primary GID from AdditionalGids, so a set-group binary can drop that group and bypass negative group permissions. Exploitation requires code execution in an affected Linux container and files whose group permission bits deny more access than their other bits.
The record
- CVE
- CVE-2022-2995
- Published
- Sep 19, 2022
- Updated
- May 29, 2025
- Vendor
- CRI-O
- Product
- CRI-O
- Classifications
- CWE-732, T1222.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 19, 2022CVE publishedPublication date reported by the CVE source.
- May 29, 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=cri-o 1.25.0
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
- permission-experiment proof of conceptfunctional · demonstrated
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