Skip to content
Fencer Vulns
medium 5.0

CVE-2019-14891 json

A flaw was found in cri-o, as a result of all pod-related processes being placed in the same memory cgroup.

published 2019-11-25 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-5999

cvss
5.0
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

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.

Patch / fix

  • kubernetes cri-o 1.16.1
  • cri-o openshift 3.11 1.11.16-0.10.dev.rhaos3.11.git1eee681.el7
  • atomic-openshift openshift 3.11 3.11.248-1.git.0.92ee8ac.el7
  • atomic-openshift-pod openshift 3.11 3.11.248-1.git.0.92ee8ac.el7
  • atomic-openshift-node openshift 3.11 3.11.248-1.git.0.92ee8ac.el7
  • atomic-openshift-tests openshift 3.11 3.11.248-1.git.0.92ee8ac.el7
  • atomic-openshift-master openshift 3.11 3.11.248-1.git.0.92ee8ac.el7
  • atomic-openshift-clients openshift 3.11 3.11.248-1.git.0.92ee8ac.el7
  • atomic-openshift-sdn-ovs openshift 3.11 3.11.248-1.git.0.92ee8ac.el7

red hat advisories RHSA-2020:2992RHSA-2020:2776

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-14891 updated cvss 5.0

cri-o: infra container reparented to systemd following OOM Killer killing it's conmon

  • Red Hat OpenShift Container Platform 3.11 cri-o 1.11.16-0.10.dev.rhaos3.11.git1eee681.el7
    fixed: vendor fix RHSA-2020:2992
  • Red Hat OpenShift Container Platform 4.2 cri-o 1.14.12-15.dev.rhaos4.2.gita17905f.el8, cri-o 1.14.12-24.dev.rhaos4.2.gita17905f.el7
    fixed: vendor fix RHSA-2020:2776
  • Red Hat OpenShift Container Platform 3.11 atomic-openshift 3.11.248-1.git.0.92ee8ac.el7, atomic-openshift-pod 3.11.248-1.git.0.92ee8ac.el7, atomic-openshift-node 3.11.248-1.git.0.92ee8ac.el7, atomic-openshift-tests 3.11.248-1.git.0.92ee8ac.el7, atomic-openshift-master 3.11.248-1.git.0.92ee8ac.el7, atomic-openshift-clients 3.11.248-1.git.0.92ee8ac.el7, +8 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.0 5.0 CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
NVD 3.1 5.0 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
NVD 2.0 6.0 AV:N/AC:M/Au:S/C:P/I:P/A:P

Affected products

  • n/a cri-o

Classification

Weakness
  • CWE-460 Improper Cleanup on Thrown Exception
  • CWE-754 Improper Check for Unusual or Exceptional Conditions

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.