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.
{
"versions": [
{
"introduced": "1.19.0"
},
{
"fixed": "1.19.6"
},
{
"introduced": "1.20.0"
},
{
"fixed": "1.20.7"
},
{
"introduced": "1.21.0"
},
{
"fixed": "1.21.6"
},
{
"introduced": "1.22.0"
},
{
"fixed": "1.22.3"
},
{
"introduced": "1.23.0"
},
{
"fixed": "1.23.2"
}
]
}