In Eclipse Jetty, for HTTP/1, HTTP/2 and HTTP/3 requests, there is no strict check that the request authority (host and port) matches what provided in the Host header (if present). This was not enforced in earlier HTTP RFC (for example, in RFC 2616), but it is in the latest RFC (9110 and 9112). This mismatch can cause a number of problems that may be classified as vulnerabilities such as: * URI constructions (for example, for redirects -- this is typical for login pages) * Virtual host selection * Reverse proxying * Misleading logs * Etc. Given that the latest RFCs require that request authority and Host header must match, Jetty should enforce this invariant.
| Vendor | Product | Versions |
|---|---|---|
| eclip | jetty | maven/org.eclipse.jetty:jetty-server: >= 9.4.0.v20161208, <= 9.4.58.v20250814, maven/org.eclipse.jetty:jetty-server: >= 10.0.0, <= 10.0.26, maven/org.eclipse.jetty:jetty-server: >= 11.0.0, <= 11.0.26, maven/org.eclipse.jetty:jetty-server: >= 12.0.0, <= 12.0.34, maven/org.eclipse.jetty:jetty-server: >= 12.1.0, <= 12.1.8 |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| eclip | jetty | cert_advisory | 90% |
| maven | org.eclipse.jetty:jetty-server | GHSA | 85% |
| realobjects | pdfreactor | cert_advisory | 90% |
Loading…
Updated affected versions to include 9.4.60, 10.0.28, 11.0.28, 12.0.34, and changed severity to CRITICAL.
Initial creation
