Jetty accepts "+" prefixed value in Content-Length
Published 14 Sept 2023 · Updated 10 Sept 2026
Is your project on an affected org.eclipse.jetty:jetty-http?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=9.0.0 <9.4.52
- Fixed in
- 9.4.52
mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-http -DdepVersion=9.4.52 -DforceVersion=true- Affected
- >=10.0.0 <10.0.16
- Fixed in
- 10.0.16
mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-http -DdepVersion=10.0.16 -DforceVersion=true- Affected
- >=11.0.0 <11.0.16
- Fixed in
- 11.0.16
mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-http -DdepVersion=11.0.16 -DforceVersion=true- Affected
- >=12.0.0 <12.0.1
- Fixed in
- 12.0.1
mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-http -DdepVersion=12.0.1 -DforceVersion=trueDetails
Impact
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.
Workarounds
There is no workaround as there is no known exploit scenario.
Original Report
RFC 9110 Secion 8.6 defined the value of Content-Length header should be a string of 0-9 digits. However we found that Jetty accepts "+" prefixed Content-Length, which could lead to potential HTTP request smuggling.
Payload:
POST / HTTP/1.1 Host: a.com Content-Length: +16 Connection: close 0123456789abcdef
When sending this payload to Jetty, it can successfully parse and identify the length.
When sending this payload to NGINX, Apache HTTPd or other HTTP servers/parsers, they will return 400 bad request.
This behavior can lead to HTTP request smuggling and can be leveraged to bypass WAF or IDS.
Is GHSA-hmr7-m48g-48f6 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.eclipse.jetty:jetty-http, and gives you the command that fixes it.
More advisories for org.eclipse.jetty:jetty-http
- HighCVE-2026-2332Jetty has HTTP Request Smuggling via Chunked Extension Quoted-String Parsing · 14 Apr 2026
- LowCVE-2025-11143org.eclipse.jetty:jetty-http has different parsing of invalid URIs · 5 Mar 2026
- MediumCVE-2024-6763Eclipse Jetty URI parsing of invalid authority · 14 Oct 2024
- LowCVE-2022-2047Jetty invalid URI parsing may produce invalid HttpURI.authority · 7 Jul 2022
References
- Linkgithub.com/eclipse/jetty.project/security/advisories/GHSA-hmr7-m48g-48f6
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-40167
- Packagegithub.com/eclipse/jetty.project
- Linklists.debian.org/debian-lts-announce/2023/09/msg00039.html
- Linkwww.debian.org/security/2023/dsa-5507
- Linkwww.rfc-editor.org/rfc/rfc9110#section-8.6
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.