Cri-o: pods are able to break out of resource confinement on cgroupv2
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | Red Hat OpenShift Container Platform 4.13 | affected |
|
||||||
| Red Hat | Red Hat OpenShift Container Platform 4.14 | affected |
|
||||||
| Red Hat | Red Hat OpenShift Container Platform 3.11 | unknown | — |
Configuration 1 [-]
|
Configuration 2 [-]
| AND |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.13 | |||
| cri-o-0:1.26.4-6.1.rhaos4.13.git9eb9cf3.el9 | cpe:/a:redhat:openshift:4.13::el8 | RHSA-2024:0195 | 2024-01-17T00:00:00Z |
| Red Hat OpenShift Container Platform 4.14 | |||
| cri-o-0:1.27.2-7.rhaos4.14.git1cc7a64.el8 | cpe:/a:redhat:openshift:4.14::el8 | RHSA-2024:0207 | 2024-01-17T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-0390 | A flaw was found in CRI-O that involves an experimental annotation leading to a container being unconfined. This may allow a pod to specify and get any amount of memory/cpu, circumventing the kubernetes scheduler and potentially resulting in a denial of service in the node. |
Github GHSA |
GHSA-p4rx-7wvg-fwrc | CRI-O's pods can break out of resource confinement on cgroupv2 |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.859% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Allocation of Resources Without Limits or Throttling