5.0
Moyenne
CVE-2019-14891 A flaw was found in cri-o, as a result of all pod-related processes being placed in the same memory cgroup
Description
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.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| cri-o | Versions non publiées |
Autres CVE de cri-o
Les 6 CVE de cri-o →
CVE-2022-2995
Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information…
7.1
Élevée
CVE-2022-1708
A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the…
Non notée
CVE-2022-27652
A flaw was found in cri-o, where containers were incorrectly started with non-empty default permissions
Non notée
CVE-2022-0811
A flaw was found in CRI-O in the way it set kernel options for a pod
Non notée