CVE-2023-26049: Infoleak

Published Apr 18, 2023
·
Updated

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: DISPLAYLANGUAGE="b; JSESSIONID=1337; c=d" will be parsed as one cookie, with the name DISPLAYLANGUAGE 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 DISPLAYLANGUAGE cookie value is rendered on the page, an attacker can smuggle the JSESSIONID cookie into the DISPLAYLANGUAGE 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.

Other sources

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:

DISPLAYLANGUAGE="b; JSESSIONID=1337; c=d" will be parsed as one cookie, with the name DISPLAYLANGUAGE 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 DISPLAYLANGUAGE cookie value is rendered on the page, an attacker can smuggle the JSESSIONID cookie into the DISPLAYLANGUAGE 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

Affected Software

24 affected componentsFixes available
maven/org.eclipse.jetty:jetty-server<9.4.51.v20230217
9.4.51.v20230217
maven/org.eclipse.jetty:jetty-server>=12.0.0alpha0<12.0.0.beta0
12.0.0.beta0
maven/org.eclipse.jetty:jetty-server>=11.0.0<11.0.14
11.0.14
maven/org.eclipse.jetty:jetty-server>=10.0.0<10.0.14
10.0.14
debian/jetty9<=9.4.16-0+deb10u1
9.4.50-4+deb10u19.4.39-3+deb11u29.4.50-4+deb11u19.4.50-4+deb12u29.4.53-1
Eclipse Jetty<9.4.51
Eclipse Jetty>=10.0.0<10.0.14
Eclipse Jetty>=11.0.0<11.0.14
Eclipse Jetty=12.0.0-alpha1
Eclipse Jetty=12.0.0-alpha2
Eclipse Jetty=12.0.0-alpha3
Debian Debian Linux=10.0
Debian Debian Linux=11.0
Debian Debian Linux=12.0
NetApp Active Iq Unified Manager Linux
NetApp Active Iq Unified Manager Windows
NetApp E-Series SANtricity OS Controller>=11.0
NetApp E-series Santricity Unified Manager
NetApp E-series Santricity Web Services
redhat/jetty-server<9.4.51
9.4.51
redhat/jetty-server<10.0.14
10.0.14
redhat/jetty-server<11.0.14
11.0.14
redhat/jetty-server<12.0.0.
12.0.0.
IBM IBM® Db2® on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data<=v4.8 v5.0v5.1v5.2v5.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.eclipse.jetty:jetty-server to a version that resolves this vulnerability.

    Fixed in 9.4.51.v20230217
  2. Upgrade

    Upgrade maven/org.eclipse.jetty:jetty-server to a version that resolves this vulnerability.

    Fixed in 12.0.0.beta0
  3. Upgrade

    Upgrade maven/org.eclipse.jetty:jetty-server to a version that resolves this vulnerability.

    Fixed in 11.0.14
  4. Upgrade

    Upgrade maven/org.eclipse.jetty:jetty-server to a version that resolves this vulnerability.

    Fixed in 10.0.14
  5. Upgrade

    Upgrade debian/jetty9 to a version that resolves this vulnerability.

    Fixed in 9.4.50-4+deb10u1Fixed in 9.4.39-3+deb11u2Fixed in 9.4.50-4+deb11u1Fixed in 9.4.50-4+deb12u2Fixed in 9.4.53-1
  6. Upgrade

    Upgrade redhat/jetty-server to a version that resolves this vulnerability.

    Fixed in 9.4.51
  7. Upgrade

    Upgrade redhat/jetty-server to a version that resolves this vulnerability.

    Fixed in 10.0.14
  8. Upgrade

    Upgrade redhat/jetty-server to a version that resolves this vulnerability.

    Fixed in 11.0.14
  9. Upgrade

    Upgrade redhat/jetty-server to a version that resolves this vulnerability.

    Fixed in 12.0.0.
  10. Upgrade

    Upgrade debian/jetty9 to a version that resolves this vulnerability.

    Fixed in 9.4.50-4+deb10u1
  11. Upgrade

    Upgrade debian/jetty9 to a version that resolves this vulnerability.

    Fixed in 9.4.39-3+deb11u2
  12. Upgrade

    Upgrade debian/jetty9 to a version that resolves this vulnerability.

    Fixed in 9.4.50-4+deb11u1
  13. Upgrade

    Upgrade debian/jetty9 to a version that resolves this vulnerability.

    Fixed in 9.4.50-4+deb12u2
  14. Upgrade

    Upgrade debian/jetty9 to a version that resolves this vulnerability.

    Fixed in 9.4.53-1

Event History

Apr 18, 2023
CVE Published
09:15 PM
Advisory Published
10:19 PM
Aug 31, 2023
Data Sourced
via Red Hat·12:42 AM
DescriptionSeverityAffected Software
Jun 19, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2023-26049?

CVE-2023-26049 is a vulnerability in Eclipse Jetty that could allow a remote authenticated attacker to obtain sensitive information by tampering with the cookie parsing mechanism.

2

How does CVE-2023-26049 impact Jetty?

CVE-2023-26049 impacts Jetty by allowing an attacker to smuggle cookies within other cookies or perform unintended behavior by tampering with the cookie parsing mechanism.

3

Which versions of Jetty are affected by CVE-2023-26049?

Jetty versions 9.4.51, 9.4.51.v20230217, 10.0.14, 11.0.14, and 12.0.0.beta0 are affected by CVE-2023-26049.

4

What is the severity of CVE-2023-26049?

CVE-2023-26049 has a severity rating of 4.5 (medium).

5

How can I fix CVE-2023-26049?

To fix CVE-2023-26049, update Jetty to version 9.4.51, 9.4.51.v20230217, 10.0.14, 11.0.14, or 12.0.0.beta0.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203