CVE-2024-8184: Eclipse Jetty's ThreadLimitHandler.getRemote() vulnerable to remote DoS attacks
5.9
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.4515%
CWE
Published
10/14/2024
Updated
11/8/2024
KEV Status
No
Technology
Java
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| org.eclipse.jetty:jetty-server | maven | >= 12.0.0, <= 12.0.8 | 12.0.9 |
| org.eclipse.jetty:jetty-server | maven | >= 10.0.0, <= 10.0.23 | 10.0.24 |
| org.eclipse.jetty:jetty-server | maven | >= 11.0.0, <= 11.0.23 | 11.0.24 |
| org.eclipse.jetty:jetty-server | maven | >= 9.3.12, <= 9.4.55 | 9.4.56 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability documentation explicitly identifies ThreadLimitHandler.getRemote() as the vulnerable component. The CWE-400/770 classifications indicate uncontrolled resource consumption, consistent with the described OOM attack vector. The pull request #11723 modifying ThreadLimitHandler and the workaround recommendation to avoid it further corroborate this as the vulnerable entry point. The method's role in tracking connections likely creates unbounded memory allocation when handling malicious requests.