CVE-2024-8184

There exists a security vulnerability in Jetty's ThreadLimitHandler.getRemote() which can be exploited by unauthorized users to cause remote denial-of-service (DoS) attack. By repeatedly sending crafted requests, attackers can trigger OutofMemory errors and exhaust the server's memory.

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.

Impact

Remote DOS attack can cause out of memory

Description

There exists a security vulnerability in Jetty's ThreadLimitHandler.getRemote() which can be exploited by unauthorized users to cause remote denial-of-service (DoS) attack. By repeatedly sending crafted requests, attackers can trigger OutofMemory errors and exhaust the server's memory.

Affected Versions

• Jetty 12.0.0-12.0.8 (Supported)
• Jetty 11.0.0-11.0.23 (EOL)
• Jetty 10.0.0-10.0.23 (EOL)
• Jetty 9.3.12-9.4.55 (EOL)

Patched Versions

• Jetty 12.0.9
• Jetty 11.0.24
• Jetty 10.0.24
• Jetty 9.4.56

Workarounds

Do not use ThreadLimitHandler.
Consider use of QoSHandler instead to artificially limit resource utilization.

References

Jetty 12 - https://github.com/jetty/jetty.project/pull/11723

Root has patched CVE-2024-8184 in the org.eclipse.jetty:jetty-server package for Root:Maven. Multiple fixed versions available.

There exists a security vulnerability in Jetty's ThreadLimitHandler.getRemote() which can be exploited by unauthorized users to cause remote denial-of-service (DoS) attack. By repeatedly sending crafted requests, attackers can trigger OutofMemory errors and exhaust the server's memory.

TuxCare rebuilt 2 packages to address 2 CVEs. Fixed in 9.4.53.v20231009-tuxcare.1.

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 5 CVEs. Fixed in 9.4.24.v20191120-tuxcare.2.

TuxCare rebuilt 3 packages to address 4 CVEs. Fixed in 11.0.18-tuxcare.1.

TuxCare rebuilt 3 packages to address 4 CVEs. Fixed in 11.0.19-tuxcare.4.

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

This update for jetty-minimal fixes the following issues:

• CVE-2024-8184: Fixed remote denial-of-service in ThreadLimitHandler.getRemote() (bsc#1231651).