CVE-2023-26049

Cookie parsing of quoted values can exfiltrate values from other cookies in Eclipse Jetty

MEDIUM
5.3
CVSS Score
Published: April 18, 2023 at 08:35 PM UTC
Updated: June 17, 2026 at 05:42 AM UTC
6 products affected across 3 vendorsDebian LinuxActive IQ Unified ManagerE Series Santricity OS Controller

Using jetty.project by eclipse?

Get instant alerts when new vulnerabilities affect jetty.project - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 1%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.14v < 11.0.14v < 12.0.0.beta0v < 9.4.5110.0.0 ≤ v < 10.0.1411.0.0 ≤ v < 11.0.1412.0.0 alpha112.0.0 alpha212.0.0 alpha3
Affected range stops below 10.0.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 11.0.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 12.0.0.beta0, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.51, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-200NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card