MediumGHSA-p4rx-7wvg-fwrcCVE-2023-6476GO-2024-2458

CRI-O's pods can break out of resource confinement on cgroupv2

Published 10 Jan 2024 · Updated 28 Jun 2024

Is your project on an affected github.com/cri-o/cri-o?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.29.0 <1.29.1
Fixed in
1.29.1
Update to the fixed version for your release line, for example:go get github.com/cri-o/cri-o@v1.29.1
Affected
>=1.28.0 <1.28.3
Fixed in
1.28.3
Update to the fixed version for your release line, for example:go get github.com/cri-o/cri-o@v1.28.3
Affected
<1.27.3
Fixed in
1.27.3
Update to the fixed version for your release line, for example:go get github.com/cri-o/cri-o@v1.27.3

Details

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 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 . 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?_

Is GHSA-p4rx-7wvg-fwrc in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/cri-o/cri-o, and gives you the command that fixes it.

More advisories for github.com/cri-o/cri-o

  • LowCVE-2025-4437CRI-O has Potential High Memory Consumption from File Read in github.com/cri-o/cri-o · 29 Aug 2025
  • MediumCVE-2025-4437CRI-O has Potential High Memory Consumption from File Read · 20 Aug 2025
  • LowCVE-2025-0750CRI-O Path Traversal vulnerability in github.com/cri-o/cri-o · 29 Jan 2025
  • MediumCVE-2025-0750CRI-O Path Traversal vulnerability · 28 Jan 2025
  • LowCVE-2024-8676CRI-O: Maliciously structured checkpoint file can gain arbitrary node access in github.com/cri-o/cri-o · 4 Dec 2024
  • MediumCVE-2024-8676CRI-O: Maliciously structured checkpoint file can gain arbitrary node access · 26 Nov 2024
All 25 advisories for github.com/cri-o/cri-o

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.