Cri-O vulnerabilitiesRanked by how likely they are to be used.
Cri-O is made by Kubernetes. We track 10 published vulnerabilities in it, across 190 versions. None of them is on the list of flaws known to be exploited today. If you run Cri-O, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Cri-O vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Cri-O's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Cri-O flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 19%CVE-2022-0811High
A flaw was found in CRI-O in the way it set kernel options for a pod.
- 3.2%CVE-2022-1708High
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.
- 2.0%CVE-2018-1000400High
Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the handling of ambient capabilities that can result in containers running with elevated privileges,...
- 1.2%CVE-2024-5154High
A flaw was found in cri-o. A malicious container can create a symbolic link to arbitrary files on the host via directory traversal (“../“).
- 0.8%CVE-2019-14891Medium
A flaw was found in cri-o, as a result of all pod-related processes being placed in the same memory cgroup.
- 0.8%CVE-2022-0532Medium
An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier.
- 0.4%CVE-2022-2995High
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...
- 0.3%CVE-2022-4318High
A vulnerability was found in cri-o. This issue allows the addition of arbitrary lines into /etc/passwd by use of a specially crafted environment variable.
- 0.2%CVE-2022-27652Medium
A flaw was found in cri-o, where containers were incorrectly started with non-empty default permissions.
- 0.2%CVE-2022-3466Medium
The version of cri-o as released for Red Hat OpenShift Container Platform 4.9.48, 4.10.31, and 4.11.6 via RHBA-2022:6316, RHBA-2022:6257, and RHBA-2022:6658, respectively, included an incorrect version of cri-o...
Running Cri-O? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Cri-O on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 10 published vulnerabilities listed under the name Cri-O, across 190 versions.
None of Cri-O's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Cri-O. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.