CVE-2023-24536 Details
Description
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=.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Feb 12, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://go.dev/cl/482075 | CVE | Patch |
| https://go.dev/cl/482076 | CVE | Patch |
| https://go.dev/cl/482077 | CVE | Patch |
| https://go.dev/issue/59153 | CVE | Issue TrackingPatch |
| https://groups.google.com/g/golang-announce/c/Xdv6JL9ENs8 | CVE | Mailing List |
| https://pkg.go.dev/vuln/GO-2023-1705 | CVE | Vendor Advisory |
| https://security.gentoo.org/glsa/202311-09 | CVE | |
| https://security.netapp.com/advisory/ntap-20230526-0007/ | CVE | |
| https://go.dev/cl/482075 | [email protected] | Patch |
| https://go.dev/cl/482076 | [email protected] | Patch |
| https://go.dev/cl/482077 | [email protected] | Patch |
| https://go.dev/issue/59153 | [email protected] | Issue TrackingPatch |
| https://groups.google.com/g/golang-announce/c/Xdv6JL9ENs8 | [email protected] | Mailing List |
| https://pkg.go.dev/vuln/GO-2023-1705 | [email protected] | Vendor Advisory |
| https://security.gentoo.org/glsa/202311-09 | [email protected] | |
| https://security.netapp.com/advisory/ntap-20230526-0007/ | [email protected] |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-770 | Allocation of Resources Without Limits or Throttling | [email protected] |
| CWE-770 | Allocation of Resources Without Limits or Throttling | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| golang go | < 1.19.8 >= 1.20.0, < 1.20.3 |
CPE
Remediation
| |
Change History
9 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Feb 12, 2025 | CVE Modified | CISA-ADP |
| Nov 21, 2024 | CVE Modified | CVE |
| May 14, 2024 | CVE Modified | [email protected] |
| Nov 25, 2023 | CVE Modified | [email protected] |
| Nov 7, 2023 | CVE Modified | [email protected] |
| May 26, 2023 | CVE Modified | [email protected] |
| Apr 17, 2023 | Initial Analysis | [email protected] |