cri-o: infra container reparented to systemd following OOM Killer killing it's conmon
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | cri-o | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | |||
| cri-o-0:1.11.16-0.10.dev.rhaos3.11.git1eee681.el7 | cpe:/a:redhat:openshift:3.11::el7 | RHSA-2020:2992 | 2020-07-27T00:00:00Z |
| Red Hat OpenShift Container Platform 4.2 | |||
| cri-o-0:1.14.12-15.dev.rhaos4.2.gita17905f.el8 | cpe:/a:redhat:openshift:4.2::el7 | RHSA-2020:2776 | 2020-07-01T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2019-5999 | 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. |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.796% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.