CVE-2023-6476: Cri-o: pods are able to break out of resource confinement on cgroupv2
Red Hat · Red Hat OpenShift Container Platform 4.13
Vendor fix available · Affected: Red Hat OpenShift Container Platform 4.13 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 59% of scored CVEs
DescriptionCVE.org
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.
Affected products3
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Red Hat · Red Hat OpenShift Container Platform 4.13Versions not stated
- Red Hat · Red Hat OpenShift Container Platform 4.14Versions not stated
- Red Hat · Red Hat OpenShift Container Platform 3.11Versions not stated
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Red Hat
- Published
- January 2024
CoverageNo articles yet
No CyberSIXT article names CVE-2023-6476 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.