CyberRota Analysis
AI-GeneratedEclipse Jetty is vulnerable due to a lack of strict validation between the request authority and the Host header for HTTP/1, HTTP/2, and HTTP/3 requests. This oversight can lead to issues such as improper URI constructions, incorrect virtual host selection, and misleading logs, potentially exposing applications to security risks. Organizations using Jetty should prioritize addressing this vulnerability to ensure compliance with the latest HTTP standards and mitigate associated risks.
Original NVD Description
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.
Related CVEs
Other vulnerabilities affecting the same vendor(s)