Kubernetes CRI-O 0.2

CPE Details

Kubernetes CRI-O 0.2
kubernetes
cri-o
0.2
2019-11-04
17h09 +00:00
2019-11-04
17h09 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:kubernetes:cri-o:0.2:*:*:*:*:*:*:*

Informations

Vendor

kubernetes

Product

cri-o

Version

0.2

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2022-1708 2022-06-07 15h43 +00:00 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 file corresponding to the output of the command is read in. Thus, if the output of the command is large it is possible to exhaust the memory or the disk space of the node when CRI-O reads the output of the command. The highest threat from this vulnerability is system availability.
7.5
High
CVE-2022-0532 2022-02-09 21h05 +00:00 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.
4.2
Medium
CVE-2019-14891 2019-11-25 09h31 +00:00 A flaw was found in cri-o, as a result of all pod-related processes being placed in the same memory cgroup. This can result in container management (conmon) processes being killed if a workload process triggers an out-of-memory (OOM) condition for the cgroup. An attacker could abuse this flaw to get host network access on an cri-o host.
5
Medium
CVE-2018-1000400 2018-05-18 16h00 +00:00 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, allowing users abilities they should not have. This attack appears to be exploitable via container execution. This vulnerability appears to have been fixed in 1.9.
8.8
High