CVE-2022-1708

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

Published Jun 7, 2022 CVSS 3.1 · 7.5 High EPSS 3.2% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2022-6034 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.
Github GHSA Github GHSA GHSA-fcm2-6c3h-pg6j Node DOS by way of memory exhaustion through ExecSync request in CRI-O
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Aug 3, 2024, 12:10 AM
Reserved
May 13, 2022, 12:00 AM
Status
Modified
Published
Jun 7, 2022, 6:15 PM
Modified
Jun 17, 2026, 4:22 AM
Severity
Moderate
Public date
Jun 6, 2022, 12:00 AM