Lack of data validation In jetty9

Description

org.eclipse.jetty:jetty-http has different parsing of invalid URIs The Jetty URI parser has some key differences compared to other common parsers when evaluating invalid or unusual URIs. Specifically:

Invalid Scheme

URI
Jetty
uri-js (nodejs)
node-url(nodejs)

Improper IPv4 mapped IPv6

URI
Jetty
System.Uri(CSharp)
curl(C)

Incorrect IPv6 delimeter priority

URI
Jetty
urllib3(python)
furl(python)
Spring
chromium

Incorrect delimeter priority

URI
Jetty
urllib3(python)
jersey

Impact

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.

Patches

Patched in Supported Open Source versions.

    12.1.5 - Supported and available on Maven Central

    12.0.31 - Supported and available on Maven Central

    11.0.x - EOL Release, patches available on tuxcare and herodevs

    10.0.x - EOL Release, patches available on tuxcare and herodevs

    9.4.x - EOL Release, patches available on tuxcare and herodevs

Workarounds

None

Resources

Mitigation

Update Impact

Minimal update. May introduce new vulnerabilities or breaking changes.

Ecosystem
Package
Affected version
Patched versions