CVE-2023-6476: GO-2024-2458 - CRI-O's pods can break out of resource confinement on cgroupv2 in github.com/cri-o/cri-o

CVE-2023-6476 · Severity: low · CVSS 3.1 · Published 2024-06-28

CRI-O's pods can break out of resource confinement on cgroupv2 in github.com/cri-o/cri-o

Technologies: github.com/cri-o/cri-o (Go). Vendors: Go.

Quick answers

Is CVE-2023-6476 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2023-6476 being exploited in the wild.
How severe is CVE-2023-6476?
Low severity, with a CVSS score of 3.1, published 28 June 2024.
Which products and versions are affected?
github.com/cri-o/cri-o (Go) SEMVER:introduced=0,fixed=1.27.3,introduced=1.28.0,fixed=1.28.3,introduced=1.29.0,fixed=1.29.1, SEMVER:introduced=1.29.0,fixed=1.29.1.
Is there a fix for CVE-2023-6476?
Yes. github.com/cri-o/cri-o (Go): upgrade to 1.29.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2023-6476?
Check whether you run github.com/cri-o/cri-o (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/cri-o/cri-o (Go): upgrade to 1.29.1 or later
    go get github.com/cri-o/cri-o@v1.29.1

Affected products

  • github.com/cri-o/cri-o (Go) SEMVER:introduced=0,fixed=1.27.3,introduced=1.28.0,fixed=1.28.3,introduced=1.29.0,fixed=1.29.1, SEMVER:introduced=1.29.0,fixed=1.29.1

Identifiers

  • CVE-2023-6476
  • GHSA-p4rx-7wvg-fwrc
  • GO-2024-2458

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.