CVE-2022-0532 is a medium-severity (CVSS 4.2) CWE-732 vulnerability in github.com/cri-o/cri-o. A fix is available for github.com/cri-o/cri-o — see the affected versions and patch details below.
Incorrect Permission Assignment for Critical Resource in CRI-O
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-0532 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
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
An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier. The sysctls from the list of "safe" sysctls specified for the cluster will be applied to the host if an attacker is able to create a pod with a hostIPC and hostNetwork kernel namespace.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/cri-o/cri-o | all versions | 1.23.1go get github.com/cri-o/cri-o@v1.23.1 |
Affected Products
cri-okubernetesopenshift container platformredhatDetection & 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.23.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0532 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
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.
Red Hat OpenShift Container Platform (OCP) uses a vulnerable version of CRI-O, but a successful exploit requires access to at least `hostnetwork` SCC (Security Context Constraints) or `privileged` SCC. The default `restricted` SCC blocks this vulnerability.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 4.10 | cri-o-0:1.23.0-92.rhaos4.10.gitdaab4d1.el7 | RHSA-2022:0055 |
| Red Hat OpenShift Container Platform 4.6 | cri-o-0:1.19.5-3.rhaos4.6.git91f8458.el7 | RHSA-2022:0866 |
| Red Hat OpenShift Container Platform 4.7 | cri-o-0:1.20.6-11.rhaos4.7.git76ea3d0.el7 | RHSA-2022:0870 |
| Red Hat OpenShift Container Platform 4.8 | cri-o-0:1.21.5-2.rhaos4.8.gitaf64931.el7 | RHBA-2022:0793 |
| Red Hat OpenShift Container Platform 4.9 | cri-o-0:1.22.2-2.rhaos4.9.gitb030be8.el7 | RHBA-2022:0794 |
Frequently Asked Questions
Is CVE-2022-0532 in your dependencies?
Find it across Go, including transitive dependencies.