CVE-2019-14891

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.

Categories

5.0
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.32%
Third-Party Advisory redhat.com
Affected: n/a cri-o
Published at:
Updated at:

References

Link Tags
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14891 issue tracking third party advisory

Frequently Asked Questions

What is the severity of CVE-2019-14891?
CVE-2019-14891 has been scored as a medium severity vulnerability.
How to fix CVE-2019-14891?
To fix CVE-2019-14891, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2019-14891 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2019-14891 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2019-14891?
CVE-2019-14891 affects n/a cri-o.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.