Security readout for executives and security teams
Plain-English summary
This CRI-O flaw can let a pod bypass resource confinement on cgroup v2 systems. A user who can create pods may cause workloads to consume more CPU or memory than intended, undermining scheduling assumptions and potentially causing node-level denial of service.
Executive priority
Prioritize within normal patch cycles for OpenShift clusters, faster for shared or multi-tenant environments. The main business risk is service disruption, not data theft.
Technical view
Red Hat describes an experimental CRI-O annotation that can make a container unconfined from resource controls. The impact is availability only: no cited confidentiality or integrity impact. CVSS 3.1 is 6.5 with low attack complexity and low privileges required.
Likely exposure
Most relevant exposure is Red Hat OpenShift Container Platform 4.13 and 4.14 using affected cri-o packages. OpenShift 3.11 status is listed as unknown in the supplied data.
Exploitation context
The supplied sources do not indicate active exploitation, and KEV is false. Exploitation requires pod-creation capability, so risk is higher in multi-tenant clusters or environments with broad developer access.
Researcher notes
Evidence is limited to Red Hat and CVE records. The affected path involves resource-control bypass through an experimental annotation, but the bundle does not provide detailed root-cause code context or fixed package versions.
Mitigation direction
- Review Red Hat CVE guidance and advisories RHSA-2024:0195 and RHSA-2024:0207.
- Update CRI-O/OpenShift through vendor-supported OpenShift channels where the advisories apply.
- Restrict who can create pods and set advanced or experimental annotations.
- Monitor node CPU and memory pressure for abnormal pod-driven consumption.
- Treat OpenShift 3.11 exposure as uncertain until vendor guidance confirms status.
Validation and detection
- Inventory OpenShift clusters and CRI-O package versions against Red Hat guidance.
- Confirm whether clusters use cgroup v2 where this issue is relevant.
- Review RBAC for users or service accounts that can create pods.
- Check admission controls for policy around experimental pod annotations.
- Look for recent node availability incidents tied to resource exhaustion.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-6476 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2024:0195CVE reference · vendor-advisory, x_refsource_REDHAT
- RHSA-2024:0207CVE reference · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2023-6476CVE reference · vdb-entry, x_refsource_REDHAT
- RHBZ#2253994CVE reference · issue-tracking, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.