Vulnerability in Kubernetes Cri-O
CVE-2022-0532
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.2 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L.
EPSS exploit prediction
EPSS: 0.008 (55.5th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 55th percentile — 55.5% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.008 · newest: 0.008 · change: 0.000
Affected products
- Kubernetes Cri-O
- Red Hat Openshift Container Platform — versions 4.0
- Cri-O — versions 1.18
Weakness classification (CWE)
Public proof-of-concept exploits
References
- bugzilla.redhat.com/show_bug.cgi (Patch, Third Party Advisory, Issue Tracking)
- kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/ (Vendor Advisory)
Frequently asked questions
- What is CVE-2022-0532?
- CVE-2022-0532 is a medium-severity vulnerability in Kubernetes Cri-O, classified under Incorrect Permission Assignment for Critical Resource. CVSS score: 4.2/10. Published 2022-02-09.
- How severe is CVE-2022-0532?
- Medium severity. CVSS v3 base score is 4.2 out of 10.
- Is CVE-2022-0532 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.