Description
Jetty is a java based web server and servlet engine. 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. 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 or its logging system. This issue has been addressed in versions 9.4.51, 10.0.14, 11.0.14, and 12.0.0.beta0 and users are advised to upgrade. There are no known workarounds for this issue.
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-3592-1 | jetty9 security update |
Debian DSA |
DSA-5507-1 | jetty9 security update |
EUVD |
EUVD-2023-1360 | Jetty is a java based web server and servlet engine. 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. 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 or its logging system. This issue has been addressed in versions 9.4.51, 10.0.14, 11.0.14, and 12.0.0.beta0 and users are advised to upgrade. There are no known workarounds for this issue. |
Github GHSA |
GHSA-p26g-97m4-6q7c | Eclipse Jetty's cookie parsing of quoted values can exfiltrate values from other cookies |
References
History
No history.
Subscriptions
Debian
Subscribe
Debian Linux
Subscribe
Eclipse
Subscribe
Jetty
Subscribe
Netapp
Subscribe
Active Iq Unified Manager
Subscribe
E-series Santricity Os Controller
Subscribe
E-series Santricity Unified Manager
Subscribe
E-series Santricity Web Services
Subscribe
Redhat
Subscribe
Amq Streams
Subscribe
Camel Spring Boot
Subscribe
Jboss Enterprise Application Platform
Subscribe
Jbosseapxp
Subscribe
Ocp Tools
Subscribe
Red Hat Single Sign On
Subscribe
Rhosemc
Subscribe
Satellite
Subscribe
Satellite Capsule
Subscribe
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-02-13T16:44:44.710Z
Reserved: 2023-02-17T22:44:03.150Z
Link: CVE-2023-26049
No data.
Status : Modified
Published: 2023-04-18T21:15:09.043
Modified: 2024-11-21T07:50:39.640
Link: CVE-2023-26049
OpenCVE Enrichment
No data.
Weaknesses
Debian DLA
Debian DSA
EUVD
Github GHSA