Eclipse Jetty has a denial of service vulnerability on DosFilterGHSA-j26w-f9rq-mr2q
MEDIUMGHSA-j26w-f9rq-mr2q is a medium-severity (CVSS 5.3) Uncontrolled Resource Consumption vulnerability in org.eclipse.jetty.ee10:jetty-ee10-servlets. A fix is available for org.eclipse.jetty.ee10:jetty-ee10-servlets — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-j26w-f9rq-mr2q.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.eclipse.jetty.ee10:jetty-ee10-servlets☕org.eclipse.jetty.ee8:jetty-ee8-servlets☕org.eclipse.jetty.ee9:jetty-ee9-servlets☕org.eclipse.jetty:jetty-servlets☕org.eclipse.jetty:jetty-servlets☕org.eclipse.jetty:jetty-servletsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Description There exists a security vulnerability in Jetty's DosFilter which can be exploited by unauthorized users to cause remote denial-of-service (DoS) attack on the server using DosFilter. By repeatedly sending crafted requests, attackers can trigger OutofMemory errors and exhaust the server's memory finally.
Vulnerability details The Jetty DoSFilter (Denial of Service Filter) is a security filter designed to protect web applications against certain types of Denial of Service (DoS) attacks and other abusive behavior. It helps to mitigate excessive resource consumption by limiting the rate at which clients can make requests to the server. The DoSFilter monitors and tracks client request patterns, including request rates, and can take actions such as blocking or delaying requests from clients that exceed predefined thresholds. The internal tracking of requests in DoSFilter is the source of this OutOfMemory condition.
Impact Users of the DoSFilter may be subject to DoS attacks that will ultimately exhaust the memory of the server if they have not configured session passivation or an aggressive session inactivation timeout.
Patches The DoSFilter has been patched in all active releases to no longer support the session tracking mode, even if configured.
Patched releases:
- 9.4.54
- 10.0.18
- 11.0.18
- 12.0.3
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.jetty.ee10:jetty-ee10-servlets | ≥ 12.0.0&&< 12.0.3 | 12.0.3org.eclipse.jetty.ee10:jetty-ee10-servlets:12.0.3 |
| ☕Maven | org.eclipse.jetty.ee8:jetty-ee8-servlets | ≥ 12.0.0&&< 12.0.3 | 12.0.3org.eclipse.jetty.ee8:jetty-ee8-servlets:12.0.3 |
| ☕Maven | org.eclipse.jetty.ee9:jetty-ee9-servlets | ≥ 12.0.0&&< 12.0.3 | 12.0.3org.eclipse.jetty.ee9:jetty-ee9-servlets:12.0.3 |
| ☕Maven | org.eclipse.jetty:jetty-servlets | ≥ 9.0.0&&< 9.4.54 | 9.4.54org.eclipse.jetty:jetty-servlets:9.4.54 |
| ☕Maven | org.eclipse.jetty:jetty-servlets | ≥ 10.0.0&&< 10.0.18 | 10.0.18org.eclipse.jetty:jetty-servlets:10.0.18 |
| ☕Maven | org.eclipse.jetty:jetty-servlets | ≥ 11.0.0&&< 11.0.18 | 11.0.18org.eclipse.jetty:jetty-servlets:11.0.18 |
Affected Products
jettyeclipseactive iq unified managernetappbootstrap osnetappDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty.ee10:jetty-ee10-servlets, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.jetty.ee10:jetty-ee10-servlets to 12.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j26w-f9rq-mr2q is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for GHSA-j26w-f9rq-mr2q (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Streams for Apache Kafka 2.8.0 | jetty-servlets | RHSA-2024:9571 |
Frequently Asked Questions
Is GHSA-j26w-f9rq-mr2q in your dependencies?
Find it across Maven, including transitive dependencies.