Skip to content
Fencer Intel
high 7.5

CVE-2017-7656 json

Jetty vulnerable to cache poisoning due to inconsistent HTTP request handling (HTTP Request Smuggling)

published 2018-06-26 8 y ago modified 2026-06-17 4 mo ago also GHSA-84q7-p226-4x5w , EUVD-2018-0544

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.1%
EPSS 6.1% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

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.

Patch / fix

  • maven org.eclipse.jetty:jetty-server 9.3.24.v20180605, 9.4.11.v20180605
  • The Eclipse Foundation Eclipse Jetty 9.3.24, 9.4.11
  • jetty9 Debian 14, Debian 13, Debian 12 9.2.25-1

debian advisories DEBIAN-CVE-2017-7656

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-7656 updated cvss 7.5

jetty: HTTP request smuggling using the range header

  • Red Hat Enterprise Linux 6 jetty-eclipse
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 jetty-io, jetty-ant, jetty-jmx, jetty-jsp, jetty-xml, jetty-http, +30 more Red Hat Fuse 7 jetty Red Hat JBoss Data Grid 7 agent-bond agent-bond
    affected: no fix available
  • Red Hat JBoss Fuse 6 jetty Red Hat JBoss Fuse Service Works 6 jetty
    affected: no fix planned “Will not fix”
  • Red Hat Satellite 5 nutch
    affected: no fix planned “Out of support scope”
  • Red Hat Software Collections rh-java-common-jetty-io, rh-java-common-jetty-ant, rh-java-common-jetty-jmx, rh-java-common-jetty-jsp, rh-java-common-jetty-xml, rh-java-common-jetty-http, +30 more
    affected: no fix available
  • Red Hat Data Grid 7.3.7
    fixed: vendor fix RHSA-2020:3779

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.11% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.eclipse.jetty:jetty-server
<9.3.24.v20180605
>=9.4.0, <9.4.11.v20180605
9.3.24.v20180605
9.4.11.v20180605

Affected products

  • The Eclipse Foundation Eclipse Jetty

Classification

Weakness
  • CWE-444 Inconsistent Interpretation of HTTP Requests

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.