| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/cri-o/cri-o | ≥ 1.19.0, < 1.19.6≥ 1.20.0, < 1.20.7≥ 1.21.0, < 1.21.6≥ 1.22.0, < 1.22.3≥ 1.23.0, < 1.23.2 | 1.19.61.20.71.21.61.22.31.23.2 |
| cri-o | ≥ 1.19.0, < 1.19.6≥ 1.20.0, < 1.20.7≥ 1.21.0, < 1.21.6≥ 1.22.0, < 1.22.3≥ 1.23.0, < 1.23.2 | 1.19.61.20.71.21.61.22.31.23.2 |
A flaw introduced in CRI-O version 1.19 which an attacker can use to bypass the safeguards and set arbitrary kernel parameters on the host. As a result, anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime can abuse the kernel.core_pattern kernel parameter to achieve container escape and arbitrary code execution as root on any node in the cluster.
The patches will be present in 1.19.6, 1.20.7, 1.21.6, 1.22.3, 1.23.2, 1.24.0
+ in the sysctl value of a pod.apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
name: sysctl-psp
spec:
forbiddenSysctls:
- "*"
However, this option will not work if any sysctls are required by any pods in the cluster.
Credit for finding this vulnerability goes to John Walker and Manoj Ahuje of Crowdstrike. The CRI-O community deeply thanks them for the report.
If you have any questions or comments about this advisory:
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free