Eclipse Jetty: HTTP Authority/Host mismatch
Eclipse Foundation Eclipse Jetty
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.eclipse.jetty:jetty-server Maven |
|
|
Eclipse Foundation Eclipse Jetty
| Product | Affected | Fixed in |
|---|---|---|
| org.eclipse.jetty:jetty-server Maven |
|
|
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.
From the CVE record · eclipse
Eclipse Jetty does not strictly check that an HTTP/1, HTTP/2, or HTTP/3 request’s authority matches its Host header when one is present. A request with mismatched values can affect redirects, virtual host selection, reverse proxying, or logs. The input does not specify authentication or user-interaction requirements.
Engineers running Maven org.eclipse.jetty:jetty-server versions 9.4.0.v20161208 through 9.4.58.v20250814, 10.0.0 through 10.0.26, 11.0.0 through 11.0.26, 12.0.0 up to but not including 12.0.35, or 12.1.0 up to but not including 12.1.9 should check their deployments.