Eclipse Jetty's cookie parsing of quoted values can exfiltrate values from other cookies
Published 18 Apr 2023 · Updated 10 Sept 2026
Is your project on an affected org.eclipse.jetty:jetty-server?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <9.4.51.v20230217
- Fixed in
- 9.4.51.v20230217
mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=9.4.51.v20230217 -DforceVersion=true- Affected
- >=10.0.0 <10.0.14
- Fixed in
- 10.0.14
mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=10.0.14 -DforceVersion=true- Affected
- >=11.0.0 <11.0.14
- Fixed in
- 11.0.14
mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=11.0.14 -DforceVersion=true- Affected
- >=12.0.0alpha0 <12.0.0.beta0
- Fixed in
- 12.0.0.beta0
mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=12.0.0.beta0 -DforceVersion=trueDetails
Nonstandard cookie parsing in Jetty may allow an attacker to smuggle cookies within other cookies, or otherwise perform unintended behavior by tampering with the cookie parsing mechanism.
If Jetty sees a cookie VALUE that starts with " (double quote), it will continue to read the cookie string until it sees a closing quote -- even if a semicolon is encountered.
So, a cookie header such as:
DISPLAY_LANGUAGE="b; JSESSIONID=1337; c=d" will be parsed as one cookie, with the name DISPLAY_LANGUAGE and a value of b; JSESSIONID=1337; c=d
instead of 3 separate cookies.
Impact
This has security implications because if, say, JSESSIONID is an HttpOnly cookie, and the DISPLAY_LANGUAGE cookie value is rendered on the page, an attacker can smuggle the JSESSIONID cookie into the DISPLAY_LANGUAGE cookie and thereby exfiltrate it. This is significant when an intermediary is enacting some policy based on cookies, so a smuggled cookie can bypass that policy yet still be seen by the Jetty server.
Patches
- 9.4.51.v20230217 - via PR #9352
- 10.0.15 - via PR #9339
- 11.0.15 - via PR #9339
Workarounds
No workarounds
References
- https://www.rfc-editor.org/rfc/rfc2965
- https://www.rfc-editor.org/rfc/rfc6265
Is GHSA-p26g-97m4-6q7c 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-server, and gives you the command that fixes it.
More advisories for org.eclipse.jetty:jetty-server
- HighCVE-2024-7708Eclipse Jetty: DoS attack triggering OutOfMemory with 100-Continue requests · 22 Jul 2026
- MediumCVE-2026-6790Eclipse Jetty: HTTP Authority/Host mismatch · 22 Jul 2026
- MediumCVE-2026-10051Eclipse Jetty: Cross-Request Leakage for trailers on HTTP/1.1 keep-alive connections · 22 Jul 2026
- HighCVE-2026-1605The Eclipse Jetty Server Artifact has a Gzip request memory leak · 5 Mar 2026
- HighCVE-2024-13009**UNSUPPORTED WHEN ASSIGNED** GzipHandler causes part of request body to be seen as request body of a separate request · 8 May 2025
- MediumCVE-2024-8184Eclipse Jetty's ThreadLimitHandler.getRemote() vulnerable to remote DoS attacks · 14 Oct 2024
References
- Linkgithub.com/eclipse/jetty.project/security/advisories/GHSA-p26g-97m4-6q7c
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-26049
- Linkgithub.com/eclipse/jetty.project/pull/9339
- Linkgithub.com/eclipse/jetty.project/pull/9352
- Packagegithub.com/eclipse/jetty.project
- Linkgithub.com/eclipse/jetty.project/releases/tag/jetty-9.4.51.v20230217
- Linklists.debian.org/debian-lts-announce/2023/09/msg00039.html
- Linksecurity.netapp.com/advisory/ntap-20230526-0001
- Linkwww.debian.org/security/2023/dsa-5507
- Linkwww.rfc-editor.org/rfc/rfc2965
- Linkwww.rfc-editor.org/rfc/rfc6265
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.