Back

HIGH

cri-o: memory exhaustion on the node when access to the kube api

Published Jun 7, 2022

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.

Affected products

Remediation

Red Hat 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.

References (8)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner redhat
Published Jun 7, 2022
Updated Aug 3, 2024
Reserved May 13, 2022
NVD
Status Modified
Modified Jun 17, 2026
Red Hat
Severity Moderate
Public date Jun 6, 2022
ENISA EUVD
Assigner redhat
Published Jun 7, 2022
Updated Aug 3, 2024
Exploited since n/a
EUVD-2022-6034 GHSA-FCM2-6C3H-PG6J