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.
2022-03-16T15:15:16.123
2024-11-21T06:39:26.720
Modified
CVSSv3.1: 8.8 (HIGH)
AV:N/AC:L/Au:S/C:C/I:C/A:C
8.0
10.0
Type | Vendor | Product | Version/Range | Vulnerable? |
---|---|---|---|---|
Application | kubernetes | cri-o | < 1.19.6 | Yes |
Application | kubernetes | cri-o | < 1.20.7 | Yes |
Application | kubernetes | cri-o | < 1.21.6 | Yes |
Application | kubernetes | cri-o | < 1.22.3 | Yes |
Application | kubernetes | cri-o | < 1.23.2 | Yes |