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
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 9.3.24, 9.4.11, 9.3.24.v20180605, 9.4.11.v20180605
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- The Eclipse Foundation Eclipse Jetty
through 9.2.0; From 9.3.0; fixed in 9.3.24; From 9.4.0; fixed in 9.4.11
- org.eclipse.jetty:jetty-serverMaven
fixed in 9.3.24.v20180605
- org.eclipse.jetty:jetty-serverMaven
From 9.4.0 · fixed in 9.4.11.v20180605
References 12
debian.org
securitytracker.com
lists.apache.org
- thread.html/708d94141126eac03011144a971a6411fcac16d9c248d1d535a39451@<solr-user.lucene.apache.org>
- thread.html/053d9ce4d579b02203db18545fee5e33f35f2932885459b74d1e4272@<issues.activemq.apache.org>
- thread.html/9317fd092b257a0815434b116a8af8daea6e920b6673f4fd5583d5fe@<commits.druid.apache.org>
- thread.html/rbf4565a0b63f9c8b07fab29352a97bbffe76ecafed8b8555c15b83c6@<issues.maven.apache.org>