Allocation of Resources Without Limits or Throttling Affecting container-tools:rhel8/slirp4netns package, versions <0:1.1.8-2.module_el8.6.0+2877+8e437bf5


Severity

Recommended
0.0
high
0
10

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.79% (83rd 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-5607979
  • published28 May 2023
  • disclosed15 Nov 2022

Introduced: 15 Nov 2022

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

How to fix?

Upgrade AlmaLinux:8 container-tools:rhel8/slirp4netns to version 0:1.1.8-2.module_el8.6.0+2877+8e437bf5 or higher.
This issue was patched in ALSA-2022:1762.

NVD Description

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

client_golang is the instrumentation library for Go applications in Prometheus, and the promhttp package in client_golang provides tooling around HTTP servers and clients. In client_golang prior to version 1.11.1, HTTP server is susceptible to a Denial of Service through unbounded cardinality, and potential memory exhaustion, when handling requests with non-standard HTTP methods. In order to be affected, an instrumented software must use any of promhttp.InstrumentHandler* middleware except RequestsInFlight; not filter any specific methods (e.g GET) before middleware; pass metric with method label name to our middleware; and not have any firewall/LB/proxy that filters away requests with unknown method. client_golang version 1.11.1 contains a patch for this issue. Several workarounds are available, including removing the method label name from counter/gauge used in the InstrumentHandler; turning off affected promhttp handlers; adding custom middleware before promhttp handler that will sanitize the request method given by Go http.Request; and using a reverse proxy or web application firewall, configured to only allow a limited set of methods.

References

CVSS Scores

version 3.1