Allocation of Resources Without Limits or Throttling Affecting podman-gvproxy package, versions <2:4.0.2-20.module+el8.8.0+18201+6ad7332c


Severity

Recommended
0.0
medium
0
10

Based on CentOS 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 ID SNYK-CENTOS8-PODMANGVPROXY-3232153
  • published 16 Jan 2023
  • disclosed 30 Nov 2022

How to fix?

Upgrade Centos:8 podman-gvproxy to version 2:4.0.2-20.module+el8.8.0+18201+6ad7332c or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream podman-gvproxy package and not the podman-gvproxy package as distributed by Centos. See How to fix? for Centos: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
Expand this section

NVD

5.3 medium
  • Attack Vector (AV)
    Network
  • Attack Complexity (AC)
    Low
  • Privileges Required (PR)
    None
  • User Interaction (UI)
    None
  • Scope (S)
    Unchanged
  • Confidentiality (C)
    None
  • Integrity (I)
    None
  • Availability (A)
    Low
Expand this section

Red Hat

5.3 medium
Expand this section

SUSE

7.5 high