Allocation of Resources Without Limits or Throttling Affecting podman-remote-debuginfo package, versions <2:4.0.2-8.module+el8.7.0+1077+0e4f03d4


Severity

Recommended
medium

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.43% (76th 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-ROCKY8-PODMANREMOTEDEBUGINFO-3271389
  • published5 Jan 2023
  • disclosed7 Jun 2022

Introduced: 7 Jun 2022

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

How to fix?

Upgrade Rocky-Linux:8 podman-remote-debuginfo to version 2:4.0.2-8.module+el8.7.0+1077+0e4f03d4 or higher.
This issue was patched in RLSA-2022:7469.

NVD Description

Note: Versions mentioned in the description apply only to the upstream podman-remote-debuginfo package and not the podman-remote-debuginfo package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux: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