high
7.5
CWE
770 400
Advisory Published
Updated

CVE-2022-41725: Excessive resource consumption in mime/multipart

First published: Tue Feb 28 2023(Updated: )

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.

Credit: security@golang.org security@golang.org security@golang.org

Affected SoftwareAffected VersionHow to fix
Golang Go<1.19.6
Golang Go=1.20.0
Golang Go=1.20.0-rc1
Golang Go=1.20.0-rc2
Golang Go=1.20.0-rc3
redhat/golang<1.20.1
1.20.1
redhat/golang<1.19.6
1.19.6
debian/golang-1.15<=1.15.15-1~deb11u4
debian/golang-1.19
1.19.8-2
IBM Concert Software<=1.0.0 - 1.0.1

Remedy

https://go.dev/cl/468124

Remedy

https://go.dev/issue/58006

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the vulnerability ID for this denial of service vulnerability?

    The vulnerability ID for this denial of service vulnerability is CVE-2022-41725.

  • What is the severity of CVE-2022-41725?

    The severity of CVE-2022-41725 is high with a CVSS score of 7.5.

  • Which software is affected by CVE-2022-41725?

    The software affected by CVE-2022-41725 is Golang Go versions 1.19.6 and 1.20.0-rc1.

  • How can the denial of service be triggered?

    The denial of service can be triggered by excessive resource consumption in net/http and mime/multipart during multipart form parsing.

  • Is there a fix available for CVE-2022-41725?

    Yes, there is a fix available for CVE-2022-41725. Users should update to Golang Go version 1.20.1.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203