Allocation of Resources Without Limits or Throttling Affecting container-tools:4.0/containers-common package, versions <2:1-35.module_el8.7.0+3344+5bcd850f


Severity

Recommended
medium

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.37% (73rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-ALMALINUX8-CONTAINERTOOLS-5615497
  • published28 May 2023
  • disclosed8 Nov 2022

Introduced: 8 Nov 2022

CVE-2022-1708  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:8 container-tools:4.0/containers-common to version 2:1-35.module_el8.7.0+3344+5bcd850f or higher.
This issue was patched in ALSA-2022:7469.

NVD Description

Note: Versions mentioned in the description apply only to the upstream container-tools:4.0/containers-common package and not the container-tools:4.0/containers-common package as distributed by AlmaLinux. See How to fix? for AlmaLinux:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1