You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vulnerable Package issue exists @ Maven-org.eclipse.jetty:jetty-http-9.4.36.v20210114 in branch main
Jetty is a java-based web server and servlet engine. In affected versions prior to 9.4.51, 10.0.x prior to 10.0.14,11.0.x prior to 11.0.14, and 12.0.x prior to 12.0.0.beta0 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. 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).
Vulnerable Package issue exists @ Maven-org.eclipse.jetty:jetty-http-9.4.36.v20210114 in branch main
Jetty is a java-based web server and servlet engine. In affected versions prior to 9.4.51, 10.0.x prior to 10.0.14,11.0.x prior to 11.0.14, and 12.0.x prior to 12.0.0.beta0 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. 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).Namespace: CxDemoInABoxRepos
Repository: Java-Webgoat
Repository Url: https://github.com/CxDemoInABoxRepos/Java-Webgoat
CxAST-Project: CxDemoInABoxRepos/Java-Webgoat
CxAST platform scan: 15076145-61a1-4d21-a896-a138ffd875d6
Branch: main
Application: Java-Webgoat
Severity: MEDIUM
State: TO_VERIFY
Status: RECURRENT
CWE: CWE-400
Additional Info
Attack vector: NETWORK
Attack complexity: LOW
Confidentiality impact: NONE
Availability impact: LOW
References
Advisory
Issue
Pull request
Commit
Pull request
Commit
Release Note
The text was updated successfully, but these errors were encountered: