First published: Tue Jun 26 2018(Updated: )
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.
Credit: emo@eclipse.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/jetty9 | 9.4.16-0+deb10u1 9.4.16-0+deb10u3 9.4.39-3+deb11u2 9.4.50-4+deb12u1 9.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 Cognos Command Center | <=10.2.4.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2017-7656.
The severity of CVE-2017-7656 is high with a severity value of 7.5.
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).
CVE-2017-7656 poses a risk of HTTP request smuggling due to a flaw in the HTTP/1.x Parser.
To mitigate the CVE-2017-7656 vulnerability, update to a version of Jetty that is not affected by the vulnerability.