CVE-2023-26048: Allocation of Resources Without Limits or Throttling
(updated )
Jetty is a java based web server and servlet engine. In affected versions servlets with multipart support (e.g. annotated with @MultipartConfig
) that call HttpServletRequest.getParameter()
or HttpServletRequest.getParts()
may cause OutOfMemoryError
when the client sends a multipart request with a part that has a name but no filename and very large content. This happens even with the default settings of fileSizeThreshold=0
which should stream the whole part content to disk. An attacker client may send a large multipart request and cause the server to throw OutOfMemoryError
. However, the server may be able to recover after the OutOfMemoryError
and continue its service – although it may take some time. This issue has been patched in versions 9.4.51, 10.0.14, and 11.0.14. Users are advised to upgrade. Users unable to upgrade may set the multipart parameter maxRequestSize
which must be set to a non-negative value, so the whole multipart content is limited (although still read into memory).
References
- github.com/eclipse/jetty.project/issues/9076
- github.com/eclipse/jetty.project/pull/9344
- github.com/eclipse/jetty.project/pull/9345
- github.com/eclipse/jetty.project/security/advisories/GHSA-qw69-rqj8-6qw8
- github.com/jakartaee/servlet/blob/6.0.0/spec/src/main/asciidoc/servlet-spec-body.adoc
- nvd.nist.gov/vuln/detail/CVE-2023-26048
Detect and mitigate CVE-2023-26048 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →