Jetty accepts "+" prefixed value in Content-Length
eclipse jetty.project
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.eclipse.jetty:jetty-http Maven |
|
|
eclipse jetty.project
| Product | Affected | Fixed in |
|---|---|---|
| org.eclipse.jetty:jetty-http Maven |
|
|
Jetty is a Java based web server and servlet engine. Prior to versions 9.4.52, 10.0.16, 11.0.16, and 12.0.1, Jetty accepts the `+` character proceeding the content-length value in a HTTP/1 header field. This is more permissive than allowed by the RFC and other servers routinely reject such requests with 400 responses. There is no known exploit scenario, but it is conceivable that request smuggling could result if jetty is used in combination with a server that does not close the connection after sending such a 400 response. Versions 9.4.52, 10.0.16, 11.0.16, and 12.0.1 contain a patch for this issue. There is no workaround as there is no known exploit scenario.
From the CVE record · GitHub_M
Jetty accepts a `+` before the Content-Length value in an HTTP/1 header, although other servers may reject the request. Request smuggling is conceivable if Jetty is paired with a server that responds with 400 but does not close the connection. No exploit scenario is known; authentication and user-interaction requirements are not specified.
Check deployments using Maven org.eclipse.jetty:jetty-http versions 9.0.0–9.4.51, 10.0.0–10.0.15, 11.0.0–11.0.15, or 12.0.0.