CR
Product
Cri-o
10
CVEs
0
On KEV
8.8
Max CVSS
0
New 30D
Severity mix
Critical 0High 6Medium 4Low 0
Watch
Add Cri-o to your stack to get only the CVEs that touch what you run.
| CVE | CVSS | Published | Summary · affected versions |
|---|---|---|---|
| CVE-2022-0811 | 8.8 | Mar 16 | A flaw was found in CRI-O in the way it set kernel options for a pod Affected: 1.19.0 before 1.19.6; 1.20.0 before 1.20.7; 1.21.0 before 1.21.6; 1.22.0 before 1.22.3; 1.23.0 before 1.23.2 |
| CVE-2018-1000400 | 8.8 | May 18 | 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… Affected: before 1.9.0 |
| CVE-2024-5154 | 8.1 | Jun 12 | A flaw was found in cri-o Affected: 1.28.6; 1.29.4; 1.30.0 |
| CVE-2022-4318 | 7.8 | Sep 25 | A vulnerability was found in cri-o Affected: All versions, or not specified |
| CVE-2022-1708 | 7.5 | Jun 7 | 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 Affected: before 1.19.7; 1.20.0 before 1.20.8; 1.21.0 before 1.21.8; 1.22.0 before 1.22.5; 1.23.0 before 1.23.3; 1.24.0 |
| CVE-2022-2995 | 7.1 | Sep 19 | 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… Affected: 1.25.0 |
| CVE-2022-3466 | 5.3 | Sep 15 | 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,… Affected: All versions, or not specified |
| CVE-2022-27652 | 5.3 | Apr 18 | A flaw was found in cri-o, where containers were incorrectly started with non-empty default permissions Affected: All versions, or not specified |
| CVE-2019-14891 | 5.0 | Nov 25 | A flaw was found in cri-o, as a result of all pod-related processes being placed in the same memory cgroup Affected: before 1.16.1 |
| CVE-2022-0532 | 4.2 | Feb 9 | An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier Affected: through 1.18 |
Showing 10