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.
{
"unresolved_ranges": [
{
"cpe": "cpe:2.3:a:redhat:openshift_container_platform:3.11:*:*:*:*:*:*:*",
"extracted_events": [
{
"last_affected": "3.11"
}
],
"source": "CPE_FIELD"
},
{
"cpe": "cpe:2.3:a:redhat:openshift_container_platform:4.1:*:*:*:*:*:*:*",
"extracted_events": [
{
"last_affected": "4.1"
}
],
"source": "CPE_FIELD"
},
{
"cpe": "cpe:2.3:a:redhat:openshift_container_platform:4.2:*:*:*:*:*:*:*",
"extracted_events": [
{
"last_affected": "4.2"
}
],
"source": "CPE_FIELD"
}
]
}