Medium severity · published Feb 9, 2022
CVE-2022-0532
An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier
4.2
CVSS
0.8%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Confidentiality
Low
Integrity
None
Availability
Low
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.8% · higher than 55% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
CR
Cri-o · Kubernetes
through 1.18 · source: NVD
OC
Openshift Container Platform · Redhat
4.0 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-0532
CVE.org
https://www.cve.org/CVERecord?id=CVE-2022-0532
Issue Tracking
https://bugzilla.redhat.com/show_bug.cgi?id=2051730
Vendor Advisory
https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#enabling-unsafe-sysctls
More from Cri-o
8.8
CVE-2022-0811
A flaw was found in CRI-O in the way it set kernel options for a pod
8.8
CVE-2018-1000400
Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the handling of ambient capabilities that can result in containers…
8.1
CVE-2024-5154
A flaw was found in cri-o
7.8
CVE-2022-4318
A vulnerability was found in cri-o
7.5
CVE-2022-1708
A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API