CVE-2017-7656: XSS

Published Jun 26, 2018
·
Updated

Eclipse Jetty is vulnerable to HTTP request smuggling, caused by a flaw in the HTTP/1.x Parser. By sending a specially-crafted request, an attacker could exploit this vulnerability to poison the web cache, bypass web application firewall protection, and conduct XSS attacks.

Other sources

In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), HTTP/0.9 is handled poorly. An HTTP/1 style request line (i.e. method space URI space version) that declares a version of HTTP/0.9 was accepted and treated as a 0.9 request. If deployed behind an intermediary that also accepted and passed through the 0.9 version (but did not act on it), then the response sent could be interpreted by the intermediary as HTTP/1 headers. This could be used to poison the cache if the server allowed the origin client to generate arbitrary content in the response.

Affected Software

6 affected componentsFixes available
debian/jetty9
9.4.16-0+deb10u19.4.16-0+deb10u39.4.39-3+deb11u29.4.50-4+deb12u19.4.53-1
Eclipse Jetty<=9.2.26
Eclipse Jetty>=9.3.0<9.3.24
Eclipse Jetty>=9.4.0<9.4.11
Debian Debian Linux=9.0
IBM GDE<=3.0.0.2

Event History

Jun 26, 2018
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
DescriptionWeakness

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 the vulnerability ID?

The vulnerability ID is CVE-2017-7656.

2

What is the severity of CVE-2017-7656?

The severity of CVE-2017-7656 is high with a severity value of 7.5.

3

How does CVE-2017-7656 affect Eclipse Jetty?

CVE-2017-7656 affects Eclipse Jetty versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled).

4

What is the risk of CVE-2017-7656?

CVE-2017-7656 poses a risk of HTTP request smuggling due to a flaw in the HTTP/1.x Parser.

5

How can I mitigate the CVE-2017-7656 vulnerability?

To mitigate the CVE-2017-7656 vulnerability, update to a version of Jetty that is not affected by the vulnerability.

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