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.
References
Link | Resource |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14891 | Issue Tracking Third Party Advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14891 | Issue Tracking Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
History
21 Nov 2024, 04:27
Type | Values Removed | Values Added |
---|---|---|
References | () https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14891 - Issue Tracking, Third Party Advisory |
Information
Published : 2019-11-25 11:15
Updated : 2024-11-21 04:27
NVD link : CVE-2019-14891
Mitre link : CVE-2019-14891
CVE.ORG link : CVE-2019-14891
JSON object : View
Products Affected
redhat
- openshift_container_platform
fedoraproject
- fedora
kubernetes
- cri-o