7.5
CWE
400 770
EPSS
0.058%
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2023-6476: Cri-o: pods are able to break out of resource confinement on cgroupv2

First published: Mon Dec 11 2023(Updated: )

### Impact _What kind of vulnerability is it? Who is impacted?_ All versions of CRI-O running on cgroupv2 nodes. Unchecked access to an experimental annotation allows a container to be unconfined. Back in 2021, [support was added](https://github.com/cri-o/cri-o/pull/4479) to support an experimental annotation that allows a user to request special resources in cgroupv2. It was supposed to be gated by an experimental annotation: `io.kubernetes.cri-o.UnifiedCgroup`, which was supposed to be filtered from the [list of allowed annotations](https://github.com/cri-o/cri-o/blob/main/pkg/config/workloads.go#L103-L107) . However, there is a bug in this code which allows any user to specify this annotation, regardless of whether it's enabled on the node. The consequences of this are a pod can specify any amount of memory/cpu and get it, circumventing the kubernetes scheduler, and potentially be able to DOS a node. ### Patches _Has the problem been patched? What versions should users upgrade to?_ 1.29.1, 1.28.3, 1.27.3 ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ use cgroupv1 ### References _Are there any links users can visit to find out more?_

Credit: secalert@redhat.com secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
go/github.com/cri-o/cri-o<1.27.3
1.27.3
go/github.com/cri-o/cri-o>=1.28.0<1.28.3
1.28.3
go/github.com/cri-o/cri-o=1.29.0
1.29.1
redhat/cri-o<1.29.1
1.29.1
redhat/cri-o<1.27.3
1.27.3
Red Hat OpenShift Container Platform=3.11
All of
Any of
Red Hat OpenShift Container Platform=4.13
Red Hat OpenShift Container Platform=4.14
Any of
Red Hat Enterprise Linux=8.0
Red Hat Enterprise Linux=9.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2023-6476?

    The severity of CVE-2023-6476 is classified as critical due to its potential impact on system security.

  • How do I fix CVE-2023-6476?

    To fix CVE-2023-6476, upgrade to CRI-O version 1.27.3, 1.28.3, or 1.29.1.

  • Who is impacted by CVE-2023-6476?

    CVE-2023-6476 impacts all versions of CRI-O running on cgroupv2 nodes.

  • What happens if I don’t address CVE-2023-6476?

    If CVE-2023-6476 is not addressed, containers may be unconfined, leading to potential security breaches.

  • Is CVE-2023-6476 present in Red Hat products?

    Yes, CVE-2023-6476 is present in specific versions of Red Hat OpenShift Container Platform and Red Hat Enterprise Linux.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203