OutOfMemoryError for large multipart without filename in Eclipse Jetty

中 5.3CVE-2023-26048 · GHSA-qw69-rqj8-6qw8 · 18/04/2023 公開 · 17/06/2026 更新

要点

CVE-2023-26048 は org.eclipse.jetty:jetty-server, jetty (eclipse) に影響する深刻度「中」 (CVSS 5.3) の脆弱性です。
今後30日間に悪用される確率（EPSS）：3.4%（全脆弱性の 88.8% より高い）。
対処：10.0.14, 11.0.14, 9.4.51.v20230217, 9.4.51 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
org.eclipse.jetty:jetty-server Maven	`≥ 10.0.0, < 10.0.14≥ 11.0.0, < 11.0.14< 9.4.51.v20230217`	`10.0.1411.0.149.4.51.v20230217`
jetty eclipse	`≥ 10.0.0, < 10.0.14≥ 11.0.0, < 11.0.14< 9.4.51`	`10.0.1411.0.149.4.51`

概要

Impact

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

A very large number of parts may cause the same problem.

Patches

Patched in Jetty versions

9.4.51.v20230217 - via PR #9345
10.0.14 - via PR #9344
11.0.14 - via PR #9344

Workarounds

Multipart parameter maxRequestSize must be set to a non-negative value, so the whole multipart content is limited (although still read into memory). Limiting multipart parameter maxFileSize won't be enough because an attacker can send a large number of parts that summed up will cause memory issues.

References

NVD の説明

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