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.
0:1.11.16-0.10.dev.rhaos3.11.git1eee681.el70:1.14.12-15.dev.rhaos4.2.gita17905f.el8Exploitability
AV:NAC:HPR:LUI:NScope
S:UImpact
C:LI:LA:L5/CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L