The Jetty URI parser has some key differences to other common parsers when evaluating invalid or unusual URIs.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 12.0.31, 12.1.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Eclipse Foundation Eclipse Jetty
From 9.4.0 · through 9.4.58; From 10.0.0 · through 10.0.26; From 11.0.0 · through 11.0.26; From 12.0.0 · through 12.0.30; From 12.1.0 · through 12.1.4
- org.eclipse.jetty:jetty-httpMaven
From 9.4.0 · through 9.4.58
- org.eclipse.jetty:jetty-httpMaven
From 10.0.0 · through 10.0.26
- org.eclipse.jetty:jetty-httpMaven
From 11.0.0 · through 11.0.26
- org.eclipse.jetty:jetty-httpMaven
From 12.0.0 · fixed in 12.0.31
- org.eclipse.jetty:jetty-httpMaven
From 12.1.0 · fixed in 12.1.5