-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CVE-2023-26048 (Medium) detected in jetty-server-11.0.12.jar - autoclosed #2533
Comments
Wiremock is used in testing only. The latest version when I checked (3.0.0-beta-7) still uses |
✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory. |
ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory. |
This was fixed in 2.5.0, but reintroduced in the main branch when #3313 was merged. |
✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory. |
CVE-2023-26048 - Medium Severity Vulnerability
Vulnerable Library - jetty-server-11.0.12.jar
The core jetty server artifact.
Library home page: https://eclipse.org/jetty
Path to dependency file: /data-prepper-plugins/s3-source/build.gradle
Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-server/11.0.12/29c82ff7e059ee1e454af6d391834abadf24e60/jetty-server-11.0.12.jar
Dependency Hierarchy:
Found in HEAD commit: ebd3e757c341c1d9c1352431bbad7bf5db2ea939
Found in base branch: main
Vulnerability Details
Jetty is a java based web server and servlet engine. In affected versions servlets with multipart support (e.g. annotated with
@MultipartConfig
) that callHttpServletRequest.getParameter()
orHttpServletRequest.getParts()
may causeOutOfMemoryError
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 offileSizeThreshold=0
which should stream the whole part content to disk. An attacker client may send a large multipart request and cause the server to throwOutOfMemoryError
. However, the server may be able to recover after theOutOfMemoryError
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 parametermaxRequestSize
which must be set to a non-negative value, so the whole multipart content is limited (although still read into memory).Publish Date: 2023-04-18
URL: CVE-2023-26048
CVSS 3 Score Details (5.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-qw69-rqj8-6qw8
Release Date: 2023-04-18
Fix Resolution: org.eclipse.jetty:jetty-server:9.4.51.v20230217,10.0.14,11.0.14;org.eclipse.jetty:jetty-runner:9.4.51.v20230217,10.0.14,11.0.14
The text was updated successfully, but these errors were encountered: