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.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
| Vendor | Product | Versions | Fixed In |
|---|---|---|---|
| kubernetes | cri-o | 1.16.1 | - |
| fedoraproject | fedora | - | - |
| redhat | openshift_container_platform |
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
5
Affected Products
2
References
kubernetes / cri-o
| - |
| - |
| redhat | openshift_container_platform | - | - |
| redhat | openshift_container_platform | - | - |
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
Exploitability
Impact