CVE-2025-11143

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 reporter

XmlParser is vulnerable to XML external entity (XXE) vulnerability. XmlParser is being used when parsing Jetty’s xml configuration files. An attacker might exploit this vulnerability in order to achieve SSRF or cause a denial of service. One possible scenario is importing a (remote) malicious WAR into a Jetty’s server, while the WAR includes a malicious web.xml.

Impact

There are no circumstances in a normally deployed Jetty server where potentially hostile XML is given to the XmlParser class without the attacker already having arbitrary access to the server. I.e. in order to exploit XmlParser the attacker would already have the ability to deploy and execute hostile code. Specifically, Jetty has no protection against malicious web application and potentially hostile web applications should only be run on an isolated virtualisation.

Thus this is not considered a vulnerability of the Jetty server itself, as any such usage of the jetty XmlParser is equally vulnerable as a direct usage of the JVM supplied SAX parser. No CVE will be allocated to this advisory.

However, any direct usage of the XmlParser class by an application may be vulnerable. The impact would greatly depend on how the application uses XmlParser, but it could be a denial of service due to large entity expansion, or possibly the revealing local files if the XML results are accessible remotely.

Patches

Ability to configure the SAXParserFactory to fit the needs of your particular XML parser implementation have been merged as part of PR #10067

Workarounds

Don't use Jetty's XmlParser to parse data from users.

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) | |---|---|---| --- | | https>://vulndetector.com/path | scheme=http>| scheme=https | invalid URI |

Improper IPv4 mapped IPv6

| URI | Jetty | System.Uri(CSharp) | curl(C) | |---|---|---| --- | | http://[0:0:0:0:0:ffff:127.0.0.1] | invalid | host=[::ffff:127.0.0.1] | host=[::ffff:127.0.0.1] | | http://[::ffff:255.255.0.0] | invalid | host=[::ffff:255.255.0.0] | host=[::ffff:255.255.0.0] |

Incorrect IPv6 delimeter priority

| URI | Jetty | urllib3(python) | furl(python) | Spring | chromium | |---|---|---| --- |---|---| | http://[normal.com@]vulndetector.com/ | host=[normal.com@] | invalid | invalid | | | | http://normal.com[user@vulndetector].com/ | host=[noirmal.com@vulndetector | | | host=normal.com| invalid | |http://normal.com[@]vulndetector.com/ | host=normal.com[@] | | | host=normal.com | invalid |

Incorrect delimeter priority

| URI | Jetty | urllib3(python) | jersey | |---|---|---| --- | | http://normal.com/#@vulndetector.com | host=vulndetector.com | host=normal.com | host=normal.com | | http://normal.com/[email protected] | host=vulndetector.com | host=normal.com | host=normal.com |

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

• Java Eclipse Jetty Report_ Incorrect Parsing Priority of the IPv6 Hostname Delimeter.pdf
• Java Eclipse Jetty Report_ The Parsing Priority of the Delimiter.pdf
• Java Eclipse Jetty Report_ Parsing Difference Due to Deformed Scheme.pdf
• Java Eclipse Jetty Report_ Improper IPv4-mapped IPv6 Parsing.pdf

Root has patched CVE-2025-11143 in the org.eclipse.jetty:jetty-http package for Root:Maven. Multiple fixed versions available.

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.

TuxCare rebuilt 2 packages to address 2 CVEs. Fixed in 9.4.59.tuxcare00001.

TuxCare rebuilt org.eclipse.jetty:jetty-http to address 1 CVE. Fixed in 11.0.27.tuxcare00001.

TuxCare rebuilt org.eclipse.jetty:jetty-http to address 1 CVE. Fixed in 10.0.27.tuxcare00001.

TuxCare rebuilt 2 org.eclipse.jetty packages to address 4 CVEs. Fixed in 9.4.53.v20231009-tuxcare.3.

TuxCare rebuilt 7 packages to address 14 CVEs. Fixed in 9.4.50.v20221201-tuxcare.1.

TuxCare rebuilt 24 packages to address 9 CVEs. Fixed in 9.4.41.v20210516-tuxcare.1.

TuxCare rebuilt 2 packages to address 2 CVEs. Fixed in 9.4.57.v20241219-tuxcare.1.

TuxCare rebuilt 2 packages to address 2 CVEs. Fixed in 9.4.24.v20191120-tuxcare.4.

These are all security issues fixed in the jetty-annotations-9.4.58-3.1 package on the GA media of openSUSE Tumbleweed.

Root has patched GHSA-wjpw-4j6x-6rwh in the org.eclipse.jetty:jetty-http package for Root:Maven. Multiple fixed versions available.

This update for jetty-minimal fixes the following issues:

• CVE-2025-11143: Fixed different parsing of invalid URIs (bsc#1259242).