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.
References
Link | Resource |
---|---|
https://access.redhat.com/errata/RHSA-2024:0195 | Vendor Advisory |
https://access.redhat.com/errata/RHSA-2024:0207 | Vendor Advisory |
https://access.redhat.com/security/cve/CVE-2023-6476 | Vendor Advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=2253994 | Issue Tracking Vendor Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
AND |
|
History
18 Jan 2024, 18:16
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2024-01-09 22:15
Updated : 2024-02-04 20:15
NVD link : CVE-2023-6476
Mitre link : CVE-2023-6476
CVE.ORG link : CVE-2023-6476
JSON object : View
Products Affected
redhat
- openshift_container_platform
- enterprise_linux
CWE
CWE-770
Allocation of Resources Without Limits or Throttling