Allocation of Resources Without Limits or Throttling Affecting container-tools:rhel8/podman-gvproxy package, versions <3:4.4.1-8.module+el8.8.0+18438+15d3aa65


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.29% (70th 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-5565571
  • published16 Jan 2023
  • disclosed30 Nov 2022

Introduced: 30 Nov 2022

CVE-2022-41717  (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.4.1-8.module+el8.8.0+18438+15d3aa65 or higher.
This issue was patched in RHSA-2023:2758.

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.

An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests. HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large keys can cause the server to allocate approximately 64 MiB per open connection.

References

CVSS Scores

version 3.1