Allocation of Resources Without Limits or Throttling Affecting container-tools:rhel8/podman-gvproxy package, versions <3:4.2.0-1.module+el8.7.0+16772+33343656


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise 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-RHEL8-CONTAINERTOOLS-4322453
  • published7 Jun 2022
  • disclosed6 Jun 2022

Introduced: 6 Jun 2022

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

How to fix?

Upgrade RHEL:8 container-tools:rhel8/podman-gvproxy to version 3:4.2.0-1.module+el8.7.0+16772+33343656 or higher.
This issue was patched in RHSA-2022:7457.

NVD Description

Note: Versions mentioned in the description apply only to the upstream container-tools:rhel8/podman-gvproxy package and not the container-tools:rhel8/podman-gvproxy package as distributed by RHEL. See How to fix? for RHEL: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