CVE search
Every published CVE plus open-source advisories (NVD, OSV, GitHub), with CVSS, EPSS and whether it is being exploited in the wild (CISA KEV). Updated every few hours. Our scans match these against the technologies they detect.
Every published CVE plus open-source advisories (NVD, OSV, GitHub), with CVSS, EPSS and whether it is being exploited in the wild (CISA KEV). Updated every few hours. Our scans match these against the technologies they detect.
| 26/11/2024 |
| GO-2022-0363 | Sysctls applied to containers with host IPC or host network namespaces can affect the host in github.com/cri-o/cri-o | 21/08/2024 |
| CVE-2024-5154 | ÉLEVÉE8.1 | A flaw was found in cri-o. A malicious container can create a symbolic link to arbitrary files on the host via directory traversal (“../“). This flaw allows the container to read and write to arbitrary files on the host system. | 12/06/2024 |
| CVE-2024-3154 | ÉLEVÉE7.2 | A flaw was found in cri-o, where an arbitrary systemd property can be injected via a Pod annotation. Any user who can create a pod with an arbitrary annotation may perform an arbitrary action on the host system. | 26/04/2024 |
| CVE-2023-6476 | ÉLEVÉE7.5 | A flaw was found in CRI-O that involves an experimental annotation leading to a container being unconfined. This may allow a pod to specify and get any amount of memory/cpu, circumventing the kubernetes scheduler and potentially resulting in a denial of service in the node. | 09/01/2024 |
| CVE-2022-4318 | ÉLEVÉE7.8 | 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. | 25/09/2023 |
| CVE-2022-2995 | ÉLEVÉE7.1 | 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 access permissions and is able to execute a binary code in that | 19/09/2022 |
| CVE-2022-1708 | ÉLEVÉE7.5 | 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 command execution, and it is read in a manner where the entire | 07/06/2022 |
| CVE-2022-27652 | MOYENNE5.3 | A flaw was found in cri-o, where containers were incorrectly started with non-empty default permissions. A vulnerability was found in Moby (Docker Engine) where containers started incorrectly with non-empty inheritable Linux process capabilities. This flaw allows an attacker with access to programs with inheritable fil | 18/04/2022 |
| CVE-2022-0811 | ÉLEVÉE8.8 | 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. | 16/03/2022 |
| GHSA-w2j5-3rcx-vx7x | MOYENNE | Sysctls applied to containers with host IPC or host network namespaces can affect the host | 15/03/2022 |
| CVE-2022-0532 | MOYENNE4.2 | An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier. The sysctls from the list of "safe" sysctls specified for the cluster will be applied to the host if an attacker is able to create a pod with a hostIPC and hostNetwork kernel namespace. | 09/02/2022 |