CVE-2023-26048
Assigner: GitHub_M
Published: 2023-04-18T20:30:20.420Z
State: PUBLISHED
title: OutOfMemoryError for large multipart without filename in Eclipse Jetty
problemTypes: descriptions: cweId: CWE-400
description: CWE-400: Uncontrolled Resource Consumption
type: CWE
metrics: cvssV3_1: attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: LOW
baseScore: 5.3
baseSeverity: MEDIUM
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
version: 3.1
affected: vendor: eclipse
product: jetty.project
versions: version: < 9.4.51
status: affected
version: >= 10.0.0, < 10.0.14
status: affected
version: >= 11.0.0, < 11.0.14
status: affected
descriptions: value: 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).
source: advisory: GHSA-qw69-rqj8-6qw8
discovery: UNKNOWN