Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.