Summary
Eclipse Jetty has a denial of service vulnerability on DosFilter
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
Impact
Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.
CVE-2024-9823 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (12.0.3, 9.4.54, 10.0.18, 11.0.18); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.eclipse.jetty.ee10:jetty-ee10-servlets to 12.0.3 or later; org.eclipse.jetty.ee8:jetty-ee8-servlets to 12.0.3 or later; org.eclipse.jetty.ee9:jetty-ee9-servlets to 12.0.3 or later; org.eclipse.jetty:jetty-servlets to 9.4.54 or later; org.eclipse.jetty:jetty-servlets to 10.0.18 or later; org.eclipse.jetty:jetty-servlets to 11.0.18 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2024-9823? CVE-2024-9823 is a medium-severity uncontrolled resource consumption vulnerability in org.eclipse.jetty.ee10:jetty-ee10-servlets (maven), affecting versions >= 12.0.0, < 12.0.3. It is fixed in 12.0.3, 9.4.54, 10.0.18, 11.0.18. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
- How severe is CVE-2024-9823? CVE-2024-9823 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2024-9823?
org.eclipse.jetty.ee10:jetty-ee10-servlets(maven) (versions >= 12.0.0, < 12.0.3)org.eclipse.jetty.ee8:jetty-ee8-servlets(maven) (versions >= 12.0.0, < 12.0.3)org.eclipse.jetty.ee9:jetty-ee9-servlets(maven) (versions >= 12.0.0, < 12.0.3)org.eclipse.jetty:jetty-servlets(maven) (versions >= 9.0.0, < 9.4.54)
- Is there a fix for CVE-2024-9823? Yes. CVE-2024-9823 is fixed in 12.0.3, 9.4.54, 10.0.18, 11.0.18. Upgrade to this version or later.
- Is CVE-2024-9823 exploitable, and should I be worried? Whether CVE-2024-9823 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-9823 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-9823?
- Upgrade
org.eclipse.jetty.ee10:jetty-ee10-servletsto 12.0.3 or later - Upgrade
org.eclipse.jetty.ee8:jetty-ee8-servletsto 12.0.3 or later - Upgrade
org.eclipse.jetty.ee9:jetty-ee9-servletsto 12.0.3 or later - Upgrade
org.eclipse.jetty:jetty-servletsto 9.4.54 or later - Upgrade
org.eclipse.jetty:jetty-servletsto 10.0.18 or later - Upgrade
org.eclipse.jetty:jetty-servletsto 11.0.18 or later
- Upgrade