Allocation of Resources Without Limits or Throttling Affecting crit package, versions <0:3.15-3.module+el8.9.0+90044+a34bc939
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 applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-ORACLE8-CRIT-6080779
- published23 Nov 2023
- disclosed28 Feb 2023
Introduced: 28 Feb 2023
CVE-2022-41725 (opens in a new tab)How to fix?
Upgrade Oracle:8 crit to version 0:3.15-3.module+el8.9.0+90044+a34bc939 or higher.
This issue was patched in ELSA-2023-6938.
NVD Description
Note: Versions mentioned in the description apply only to the upstream crit package and not the crit package as distributed by Oracle.
See How to fix? for Oracle:8 relevant fixed versions and status.
A denial of service is possible from excessive resource consumption in net/http and mime/multipart. Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files. With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous. In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct. Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.
References
- https://linux.oracle.com/cve/CVE-2022-41725.html
- https://linux.oracle.com/errata/ELSA-2023-3083.html
- https://linux.oracle.com/errata/ELSA-2023-6938.html
- https://linux.oracle.com/errata/ELSA-2023-6939.html
- https://go.dev/cl/468124
- https://go.dev/issue/58006
- https://groups.google.com/g/golang-announce/c/V0aBFqaFs_E
- https://pkg.go.dev/vuln/GO-2023-1569
- https://security.gentoo.org/glsa/202311-09