Skip to content

Eclipse Jetty's ThreadLimitHandler.getRemote() vulnerable to remote DoS attacks

Moderate severity GitHub Reviewed Published Oct 14, 2024 in jetty/jetty.project • Updated Nov 8, 2024

Package

maven org.eclipse.jetty:jetty-server (Maven)

Affected versions

>= 12.0.0, <= 12.0.8
>= 10.0.0, <= 10.0.23
>= 11.0.0, <= 11.0.23
>= 9.3.12, <= 9.4.55

Patched versions

12.0.9
10.0.24
11.0.24
9.4.56

Description

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 - jetty/jetty.project#11723

References

@joakime joakime published to jetty/jetty.project Oct 14, 2024
Published by the National Vulnerability Database Oct 14, 2024
Published to the GitHub Advisory Database Oct 14, 2024
Reviewed Oct 14, 2024
Last updated Nov 8, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.075%
(35th percentile)

Weaknesses

CVE ID

CVE-2024-8184

GHSA ID

GHSA-g8m5-722r-8whq

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.