CVSS 3.1
5.0 mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:LMedium (5.0). EPSS 0.8% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:LExplain 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.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| kubernetes:cri-o | before 1.16.1 |
| redhat:openshift_container_platform | 3.11 |
| redhat:openshift_container_platform | 4.1 |
| redhat:openshift_container_platform | 4.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Red Hat | openshift:3.11::el7 | atomic-openshift, atomic-openshift-pod, atomic-openshift-node and 10 more | 0:3.11.248-1.git.0.92ee8ac.el7 | RHSA-2020:2992 |
| Red Hat | openshift:3.11::el7 | atomic-openshift-web-console | 0:3.11.248-1.git.1.cc96c2d.el7 | RHSA-2020:2992 |
| Red Hat | openshift:3.11::el7 | cri-o, cri-o-debuginfo | 0:1.11.16-0.10.dev.rhaos3.11.git1eee681.el7 | RHSA-2020:2992 |
| Red Hat | openshift:4.2::el7 | cri-o, cri-o-debuginfo | 0:1.14.12-24.dev.rhaos4.2.gita17905f.el7 | RHSA-2020:2776 |
| Red Hat | openshift:4.2::el8 | cri-o, cri-o-debuginfo, cri-o-debugsource | 0:1.14.12-15.dev.rhaos4.2.gita17905f.el8 | RHSA-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 rates this Moderate.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | cri-o-0:1.11.16-0.10.dev.rhaos3.11.git1eee681.el7 | Fixed 2020-07-27 | RHSA-2020:2992 |
| Red Hat OpenShift Container Platform 4.2 | cri-o-0:1.14.12-15.dev.rhaos4.2.gita17905f.el8 | Fixed 2020-07-01 | RHSA-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.