CVE-2022-2995 is a high-severity (CVSS 7.1) CWE-284 vulnerability in github.com/cri-o/cri-o. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/cri-o/cri-o — see the affected versions and patch details below.
CRI-O incorrect handling of supplementary groups may lead to sensitive information disclosure
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-2995.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/cri-o/cri-oReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/cri-o/cri-o | all versions | 1.25.0go get github.com/cri-o/cri-o@v1.25.0 |
Affected Products
cri-okubernetesResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cri-o/cri-o, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cri-o/cri-o to 1.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2995 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 4.10 | cri-o-0:1.23.5-11.rhaos4.10.gitfc32aac.el7 | RHSA-2023:3216 |
| Red Hat OpenShift Container Platform 4.11 | cri-o-0:1.24.5-5.rhaos4.11.git8bf967b.el8 | RHSA-2023:3541 |
| Red Hat OpenShift Container Platform 4.12 | cri-o-0:1.25.1-5.rhaos4.12.git6005903.el8 | RHSA-2022:7398 |
Frequently Asked Questions
Is CVE-2022-2995 in your dependencies?
Find it across Go, including transitive dependencies.