Node denial of service via annotation filtering
Published Jan 9, 2024 · Updated Nov 20, 2025
Resource confinement bypass in CRI-O on OpenShift 4.13 and 4.14 allows remote authenticated users to exhaust node CPU or memory. FilterDisallowedAnnotations matches the UnifiedCgroup prefix but deletes the prefix string rather than the submitted annotation key, leaving the crafted key active. Exploitation requires permission to submit a pod to a cgroup v2 node; the resulting container can bypass scheduler limits and interrupt that node.
Summary
What happened
Resource confinement bypass in CRI-O on OpenShift 4.13 and 4.14 allows remote authenticated users to exhaust node CPU or memory. FilterDisallowedAnnotations matches the UnifiedCgroup prefix but deletes the prefix string rather than the submitted annotation key, leaving the crafted key active. Exploitation requires permission to submit a pod to a cgroup v2 node; the resulting container can bypass scheduler limits and interrupt that node.
The record
- CVE
- CVE-2023-6476
- Published
- Jan 9, 2024
- Updated
- Nov 20, 2025
- Vendor
- Red Hat
- Product
- Red Hat OpenShift Container Platform 4.14
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 9, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo