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.
[
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "3.11"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "4.1"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "4.2"
}
]
}
]
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2019-14891.json"