org.eclipse.jetty:jetty-http has different parsing of invalid URIs
Eclipse Foundation Eclipse Jetty
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.eclipse.jetty:jetty-http Maven |
|
|
Eclipse Foundation Eclipse Jetty
| Product | Affected | Fixed in |
|---|---|---|
| org.eclipse.jetty:jetty-http Maven |
|
|
The Jetty URI parser has some key differences to other common parsers when evaluating invalid or unusual URIs. Differential parsing of URIs in systems using multiple components may result in security by-pass. For example a component that enforces a black list may interpret the URIs differently from one that generates a response. At the very least, differential parsing may divulge implementation details.
From the CVE record · eclipse
The Jetty URI parser can interpret invalid or unusual URIs differently from other parsers. In systems with multiple components, an attacker may exploit those differences to bypass a security check or reveal implementation details. The input does not specify whether authentication or user interaction is required.
Check Maven applications using org.eclipse.jetty:jetty-http versions 9.4.0–9.4.58, 10.0.0–10.0.26, 11.0.0–11.0.26, 12.0.0–before 12.0.31, or 12.1.0–before 12.1.5.