CVE-2022-1708
cri-o: memory exhaustion on the node when access to the kube api
Severity
ModerateRed Hat Product Security
CVSS 3.1
Review impact separately from score.
Published · June 6, 2022
Updated · April 28, 2026
Description
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.
Statement
The vulnerability exists in reading of the output file from the ExecSync command, by the CRI-O in the Kubernetes,if the file were to be too large, then this would lead to resource exhaustion,the attack is purely theoretical in nature and would only lead to a denial of service,moreover the attacker would require code execution to exploit this making this a moderate vulnerability at best.
CVSS score applicability
The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.
Mitigation
No mitigation is specified in collected source.
CVSS / CWE
CVSS 3.1 · 6.8CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:N/A:H
CWE-770 · Allocation of Resources Without Limits or Throttling