Vulnerability in Kubernetes Cri-O
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. 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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.0 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L.
EPSS exploit prediction
EPSS: 0.008 (55.6th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 56th percentile — 55.6% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.008 · newest: 0.008 · change: -0.000
Affected products
- Kubernetes Cri-O
- Fedoraproject Fedora
- Red Hat Openshift Container Platform — versions 3.11, 4.1, 4.2
- Cri-O
Weakness classification (CWE)
Public proof-of-concept exploits
References
- bugzilla.redhat.com/show_bug.cgi (Third Party Advisory, Issue Tracking)
Frequently asked questions
- What is CVE-2019-14891?
- CVE-2019-14891 is a medium-severity vulnerability in Kubernetes Cri-O, classified under CWE-460. CVSS score: 5.0/10. Published 2019-11-25.
- How severe is CVE-2019-14891?
- Medium severity. CVSS v3 base score is 5.0 out of 10.
- Is CVE-2019-14891 known to be exploited?
- 2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.