cve.bz

CVE-2019-14891 Improper Cleanup on Thrown Exception

5.0 mediumEPSS 0.8%

Medium (5.0). EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.0 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 57th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-754 Improper Check for Unusual or Exceptional Conditions
CWE-460 Improper Cleanup on Thrown Exception
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-14891 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-14891?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-14891?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-14891 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
kubernetes:cri-obefore 1.16.1
redhat:openshift_container_platform3.11
redhat:openshift_container_platform4.1
redhat:openshift_container_platform4.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hatopenshift:3.11::el7atomic-openshift, atomic-openshift-pod, atomic-openshift-node and 10 more0:3.11.248-1.git.0.92ee8ac.el7RHSA-2020:2992
Red Hatopenshift:3.11::el7atomic-openshift-web-console0:3.11.248-1.git.1.cc96c2d.el7RHSA-2020:2992
Red Hatopenshift:3.11::el7cri-o, cri-o-debuginfo0:1.11.16-0.10.dev.rhaos3.11.git1eee681.el7RHSA-2020:2992
Red Hatopenshift:4.2::el7cri-o, cri-o-debuginfo0:1.14.12-24.dev.rhaos4.2.gita17905f.el7RHSA-2020:2776
Red Hatopenshift:4.2::el8cri-o, cri-o-debuginfo, cri-o-debugsource0:1.14.12-15.dev.rhaos4.2.gita17905f.el8RHSA-2020:2776

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's mitigation

As of cri-o v1.15 you can set conmon_cgroup = "system.slice" in the crio.runtime section of /etc/crio/crio.conf. On OpenShift Container Platform 4.x that can be done by following the documentation here:

https://access.redhat.com/documentation/en-us/openshift_container_platform/4.2/html/architecture/architecture-rhcos

For OpenShift Container Platform 3.x you can edit /etc/crio/crio.conf directly on the worker node if using cri-o on that version. Cri-o is not the default container engine on that version, Docker is.

ProductPackageStateAdvisory
Red Hat OpenShift Container Platform 3.11cri-o-0:1.11.16-0.10.dev.rhaos3.11.git1eee681.el7Fixed 2020-07-27RHSA-2020:2992
Red Hat OpenShift Container Platform 4.2cri-o-0:1.14.12-15.dev.rhaos4.2.gita17905f.el8Fixed 2020-07-01RHSA-2020:2776

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2019-14891.

References

Check your stackJSON