# CVE-2024-8184: Jetty ThreadLimitHandler.getRemote() vulnerable to remote DoS attacks > Attackers can cause remote denial of service in Jetty by exhausting server memory via crafted requests to ThreadLimitHandler. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 Oct 2024 - **Updated:** 3 Nov 2025 - **Also known as:** CLEANSTART-2026-AC10054, CLEANSTART-2026-KY67158, CLEANSTART-2026-XA09003, DEBIAN-CVE-2024-8184, GHSA-g8m5-722r-8whq, MINI-2382-3q76-8c86, MINI-78jv-6x67-6jp7, MINI-9g7c-p633-jfpj, MINI-hhjc-mhwc-67g4, MINI-qhhw-mg4p-7vm9, ROOT-APP-MAVEN-CVE-2024-8184, SUSE-SU-2024:3720-1, UBUNTU-CVE-2024-8184, openSUSE-SU-2024:14408-1 ## What is CVE-2024-8184? CVE-2024-8184 is a medium-severity denial of service vulnerability in Eclipse Jetty, published on 14 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2024-8184? 8 open source packages ship an affected version, including org.eclipse.jetty:jetty-server. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.eclipse.jetty:jetty-server` | Maven | From 10.0.0 | 10.0.24 | | `org.eclipse.jetty:jetty-server` | Maven | From 10.0.0 | 10.0.24 | | `org.eclipse.jetty:jetty-server` | Maven | From 11.0.0 | 11.0.24 | | `org.eclipse.jetty:jetty-server` | Maven | From 11.0.0 | 11.0.24 | | `org.eclipse.jetty:jetty-server` | Maven | From 12.0.0 | 12.0.9 | | `org.eclipse.jetty:jetty-server` | Maven | From 12.0.0 | 12.0.9 | | `org.eclipse.jetty:jetty-server` | Maven | From 9.3.12 | 9.4.56 | | `org.eclipse.jetty:jetty-server` | Maven | From 9.3.12 | 9.4.56 | | `jetty-minimal` | SUSE:Linux Enterprise Module for Development Tools 15 SP5 | All versions | 9.4.56-150200.3.28.1 | | `jetty-minimal` | SUSE:Linux Enterprise Module for Development Tools 15 SP6 | All versions | 9.4.56-150200.3.28.1 | | `jetty-minimal` | SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 9.4.56-150200.3.28.1 | | `jetty-minimal` | openSUSE:Leap 15.5 | All versions | 9.4.56-150200.3.28.1 | | `jetty-minimal` | openSUSE:Leap 15.6 | All versions | 9.4.56-150200.3.28.1 | | `jetty-minimal` | openSUSE:Tumbleweed | All versions | 9.4.56-2.1 | Products: Eclipse Jetty. ## How do I fix CVE-2024-8184? Upgrade org.eclipse.jetty:jetty-server to a fixed version for your release line: 10.0.24, 11.0.24, 12.0.9 or 9.4.56. ## Is CVE-2024-8184 being exploited? There is no known exploitation of CVE-2024-8184 in the wild and no public exploit code. ## Other vulnerabilities in Eclipse Jetty - [CVE-2016-4800](https://insights.sbomify.com/CVE-2016-4800/): Jetty contains an alias issue that could allow unauthenticated remote code execution due to specially crafted request (critical 9.8) - [CVE-2019-17638](https://insights.sbomify.com/CVE-2019-17638/): Operation on a Resource after Expiration or Release in Jetty Server (critical 9.4) - [CVE-2018-12538](https://insights.sbomify.com/CVE-2018-12538/): Access and integrity issue within Eclipse Jetty (high 8.8) - [CVE-2026-10050](https://insights.sbomify.com/CVE-2026-10050/): Digest authentication lossy encoding (high 8.7) - [CVE-2025-5115](https://insights.sbomify.com/CVE-2025-5115/): MadeYouReset HTTP/2 vulnerability (high 7.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-8184 and fix it if it is affected. What it is: CVE-2024-8184 is a medium-severity denial of service vulnerability in Eclipse Jetty, published on 14 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-8184 in the wild and no public exploit code. Affected packages and fixed versions: - org.eclipse.jetty:jetty-server (Maven): affected from 10.0.0; fixed in 10.0.24 - org.eclipse.jetty:jetty-server (Maven): affected from 10.0.0; fixed in 10.0.24 - org.eclipse.jetty:jetty-server (Maven): affected from 11.0.0; fixed in 11.0.24 - org.eclipse.jetty:jetty-server (Maven): affected from 11.0.0; fixed in 11.0.24 - org.eclipse.jetty:jetty-server (Maven): affected from 12.0.0; fixed in 12.0.9 - org.eclipse.jetty:jetty-server (Maven): affected from 12.0.0; fixed in 12.0.9 - org.eclipse.jetty:jetty-server (Maven): affected from 9.3.12; fixed in 9.4.56 - org.eclipse.jetty:jetty-server (Maven): affected from 9.3.12; fixed in 9.4.56 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-8184/ (Markdown: https://insights.sbomify.com/CVE-2024-8184/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8184 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8184 - OSV: https://osv.dev/vulnerability/CVE-2024-8184 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-8184/ Summaries are generated and may contain mistakes; the official description above is the record.