CVE-2023-6476GHSA-P4RX-7WVG-FWRCGO-2024-2458
Cri-o: pods are able to break out of resource confinement on cgroupv2
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.29.1, 1.28.3, 1.27.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- cri-o
Version range not reported
- cri-o
Version range not reported
- cri-o
Version range not reported
- github.com/cri-o/cri-oGo
From 1.29.0 · fixed in 1.29.1
- github.com/cri-o/cri-oGo
From 1.28.0 · fixed in 1.28.3
- github.com/cri-o/cri-oGo
fixed in 1.27.3
- github.com/cri-o/cri-oGo
fixed in 1.27.3; From 1.28.0 · fixed in 1.28.3; From 1.29.0 · fixed in 1.29.1