CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2019 · Kubernetes

CVE-2019-14891
Kubernetes Cri-o vulnerability

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.

Affected products

Cri-o, Fedora, Openshift Container Platform. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Kubernetes Cri-o runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Set the orderSystems that can be reached from the internet come first, then the rest.

References

More vulnerabilities in Kubernetes products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.