Bug 1772280 (CVE-2019-14891)
| Summary: | CVE-2019-14891 cri-o: infra container reparented to systemd following OOM Killer killing it's conmon | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Jason Shepherd <jshepherd> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | amurdaca, aos-bugs, bmontgom, dominik.mierzejewski, dwalsh, eparis, fkluknav, jbasquil, jburrell, jokerman, lsm5, nstielau, rphillips, rtillery, santiago, security-response-team, sponnaga |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | cri-o-1.16.1 | Doc Type: | If docs needed, set a value |
| Doc Text: |
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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-01 19:27:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1774269, 1774270, 1774271, 1774272, 1774273 | ||
| Bug Blocks: | 1770013 | ||
|
Description
Jason Shepherd
2019-11-14 01:23:39 UTC
Acknowledgments: Name: Nick Freeman (Capsule8) Created cri-o tracking bugs for this issue: Affects: fedora-all [bug 1774273] 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. External References: https://capsule8.com/blog/oomypod-nothin-to-cri-o-bout/ This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.2 Via RHSA-2020:2776 https://access.redhat.com/errata/RHSA-2020:2776 This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2019-14891 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 3.11 Via RHSA-2020:2992 https://access.redhat.com/errata/RHSA-2020:2992 |