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.
0:1.23.1-12.rhaos4.10.git1607c6e.el70:1.19.5-3.rhaos4.6.git91f8458.el70:1.20.6-11.rhaos4.7.git76ea3d0.el70:1.21.5-3.rhaos4.8.gitaf64931.el70:1.22.2-3.rhaos4.9.gitb030be8.el7Exploitability
AV:NAC:LPR:LUI:NScope
S:UImpact
C:HI:HA:H8.8/CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H