CVE-2019-14891
First published: Thu Nov 07 2019(Updated: )
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.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/cri-o | <0:1.11.16-0.10.dev.rhaos3.11.git1eee681.el7 | 0:1.11.16-0.10.dev.rhaos3.11.git1eee681.el7 |
| redhat/cri-o | <0:1.14.12-15.dev.rhaos4.2.gita17905f.el8 | 0:1.14.12-15.dev.rhaos4.2.gita17905f.el8 |
| Kubernetes CRI-O | <1.16.1 | |
| Fedoraproject Fedora | ||
| Redhat Openshift Container Platform | =3.11 | |
| Redhat Openshift Container Platform | =4.1 | |
| Redhat Openshift Container Platform | =4.2 |
Remedy
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.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14891
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1774273
- https://access.redhat.com/documentation/en-us/openshift_container_platform/4.2/html/architecture/architecture-rhcos
- https://capsule8.com/blog/oomypod-nothin-to-cri-o-bout/
- https://access.redhat.com/errata/RHSA-2020:2776
- https://access.redhat.com/security/cve/cve-2019-14891
- https://access.redhat.com/errata/RHSA-2020:2992
- https://bugzilla.redhat.com/show_bug.cgi?id=1772280
- https://www.cve.org/CVERecord?id=CVE-2019-14891 https://nvd.nist.gov/vuln/detail/CVE-2019-14891 https://capsule8.com/blog/oomypod-nothin-to-cri-o-bout/
Frequently Asked Questions
What is the vulnerability ID for this flaw in cri-o?
The vulnerability ID is CVE-2019-14891.
What is the severity of CVE-2019-14891?
The severity of CVE-2019-14891 is medium.
How does the flaw in cri-o affect container management processes?
The flaw can result in container management (conmon) processes being killed if a workload process triggers an out-of-memory (OOM) condition.
How can an attacker abuse the flaw in cri-o?
An attacker could abuse this flaw to cause an out-of-memory (OOM) condition and disrupt container management processes.
Which software versions are affected by CVE-2019-14891?
Cri-o versions up to and including 1.16.1 are affected.
- collector/redhat-cve
- collector/nvd-index
- agent/type
- agent/first-publish-date
- agent/weakness
- agent/softwarecombine
- agent/author
- agent/severity
- agent/remedy
- agent/description
- agent/references
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2019-14891
- agent/software-canonical-lookup
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/tags
- agent/event
- agent/trending
- package-manager/redhat
- vendor/kubernetes
- canonical/kubernetes cri-o
- vendor/fedoraproject
- canonical/fedoraproject fedora
- vendor/redhat
- canonical/redhat openshift container platform
- version/redhat openshift container platform/3.11
- version/redhat openshift container platform/4.1
- version/redhat openshift container platform/4.2