A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API.
- 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.22.5, 1.23.3, 1.24.1
- 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
Summary
A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API. The ExecSync request runs commands in a container and logs the output of the command. This output is then read by CRI-O after command execution, and it is read in a manner where the entire file corresponding to the output of the command is read in. Thus, if the output of the command is large it is possible to exhaust the memory or the disk space of the node when CRI-O reads the output of the command. The highest threat from this vulnerability is system availability.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a CRI-O
Version range not reported
- github.com/cri-o/cri-oGo
fixed in 1.22.5; From 1.23.0 · fixed in 1.23.3; From 1.24.0 · fixed in 1.24.1
- github.com/cri-o/cri-oGo
From 1.24.0 · fixed in 1.24.1
- github.com/cri-o/cri-oGo
From 1.23.0 · fixed in 1.23.3
- github.com/cri-o/cri-oGo
fixed in 1.22.5