Not rated
CVE-2022-0811 A flaw was found in CRI-O in the way it set kernel options for a pod
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.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| cri-o | Versions not published |
Other CVEs of cri-o
The 6 CVEs of cri-o →
CVE-2022-2995
Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information…
7.1
High
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…
Not rated
CVE-2022-27652
A flaw was found in cri-o, where containers were incorrectly started with non-empty default permissions
Not rated
CVE-2022-0532
An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier
Not rated