Resource Exhaustion Affecting container-tools:rhel8/podman-gvproxy package, versions <3:4.6.1-4.module+el8.9.0+19761+326da906
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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 IDSNYK-RHEL8-CONTAINERTOOLS-5413290
- published5 Apr 2023
- disclosed4 Apr 2023
Introduced: 4 Apr 2023
CVE-2023-24536 (opens in a new tab)How to fix?
Upgrade RHEL:8 container-tools:rhel8/podman-gvproxy to version 3:4.6.1-4.module+el8.9.0+19761+326da906 or higher.
This issue was patched in RHSA-2023:6939.
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.
Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.
References
- https://access.redhat.com/security/cve/CVE-2023-24536
- https://go.dev/cl/482075
- https://go.dev/cl/482076
- https://go.dev/cl/482077
- https://go.dev/issue/59153
- https://groups.google.com/g/golang-announce/c/Xdv6JL9ENs8
- https://pkg.go.dev/vuln/GO-2023-1705
- https://security.gentoo.org/glsa/202311-09
- https://security.netapp.com/advisory/ntap-20230526-0007/