High severity · published Mar 16, 2022
CVE-2022-0811
A flaw was found in CRI-O in the way it set kernel options for a pod
8.8
CVSS
19%
EPSS
No
On KEV
Description
A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deployed.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)19.0% · higher than 97% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
CR
Cri-o · Kubernetes
1.19.0 before 1.19.6; 1.20.0 before 1.20.7; 1.21.0 before 1.21.6; 1.22.0 before 1.22.3; 1.23.0 before 1.23.2 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-0811
CVE.org
https://www.cve.org/CVERecord?id=CVE-2022-0811
Issue Tracking
https://bugzilla.redhat.com/show_bug.cgi?id=2059475
Third Party Advisory
https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7
More from Cri-o
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
7.1
CVE-2022-2995
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…