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.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
| Vendor | Product | Versions | Fixed In |
|---|---|---|---|
| kubernetes | cri-o | 1.19.0 - 1.19.6 | - |
| kubernetes | cri-o | 1.20.0 - 1.20.7 | - |
| kubernetes | cri-o | 1.21.0 - 1.21.6 |
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
5
Affected Products
4
References
kubernetes / cri-o
| - |
| kubernetes | cri-o | 1.22.0 - 1.22.3 | - |
| kubernetes | cri-o | 1.23.0 - 1.23.2 | - |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Exploitability
Impact