CVE-2024-9823VulnerabilityPublished 14 Oct 2024Updated 3 Nov 2025

CVE-2024-9823: Eclipse Foundation Jetty · Uncontrolled Resource Consumption

Affects Eclipse Foundation JettySource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.eclipse.jetty/jetty`pkg:maven/org.eclipse.jetty/jetty`Other threats	Affected =9.0.0 =10.0.0 =11.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor vendor communications closely for official patches or updates addressing CVE-2024-9823 and apply them promptly once available. 2. In the interim, consider disabling the DosFilter component if it is not essential or if alternative DoS protections are in place. 3. Implement upstream rate limiting and traffic filtering at network edge devices or reverse proxies to restrict the volume of requests reaching Jetty servers. 4. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious request patterns indicative of resource exhaustion attempts. 5. Enhance server resource monitoring to detect abnormal memory usage spikes and automate alerts for potential attacks. 6. Conduct regular security assessments and penetration tests focusing on DoS resilience of Jetty deployments. 7. Where feasible, deploy Jetty instances behind load balancers that can absorb or mitigate traffic spikes. 8. Review and harden application-level request handling to minimize resource consumption per request. 9. Document and rehearse incident response plans for DoS scenarios to reduce downtime. 10. Educate development and operations teams about this vulnerability and best practices for DoS mitigation in Java-based web servers.

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.

Impact

For European organizations, the primary impact of CVE-2024-9823 is on service availability. Organizations relying on Jetty for web services, APIs, or middleware may experience outages or degraded performance due to memory exhaustion caused by malicious request floods. This can disrupt business operations, customer access, and internal processes. Sectors with high dependence on continuous web service availability, such as finance, healthcare, e-government, and telecommunications, are particularly vulnerable. The vulnerability does not compromise data confidentiality or integrity, but denial-of-service conditions can indirectly affect trust and compliance with service-level agreements (SLAs). Additionally, organizations may face reputational damage and potential regulatory scrutiny if service disruptions impact critical infrastructure or public services. The ease of exploitation and lack of authentication requirements increase the risk of opportunistic attacks, especially against publicly accessible Jetty instances. European entities using older or unpatched Jetty versions should assess exposure and prioritize mitigation to maintain operational resilience.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 20:09 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats