Cri-o vulnerabilities
We track 3 vulnerabilities in Cri-o products. 3 are rated high or critical, and none are known to be exploited. The most recent was published on September 19, 2022.
Latest Cri-o vulnerabilities
- 7.1 High severity
cri-o: Incorrect Permission Assignment for Critical Resource
Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set acce
- 7.5 High severity
CRI-O: Allocation of Resources Without Limits or Throttling
A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API. The ExecSync request runs commands in a container and logs the output of the command. This output is then read by CRI-O after com
- 8.8 High severity
CRI-O: Improper Control of Generation of Code
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 nod