CVE-2022-0811Published Mar 16, 2022 · Mar 16Updated Oct 28
Code Injection in CRI-O
CRI-O
High8.8Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/cri-o/cri-o Go |
|
|
CRI-O
| Product | Affected | Fixed in |
|---|---|---|
| github.com/cri-o/cri-o Go |
|
|
1.22.31.23.2A 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.
From the CVE record · redhat
CRI-O is vulnerable in how it sets kernel options for a pod. Someone with permission to deploy a pod on a Kubernetes cluster using CRI-O can escape the container and execute arbitrary code as root on the node where the pod is deployed.
Check Kubernetes clusters using the Go package github.com/cri-o/cri-o at versions >=1.19.0 <1.19.6, >=1.20.0 <1.20.7, >=1.21.0 <1.21.6, >=1.22.0 <1.22.3, or >=1.23.0 <1.23.2.