CVE-2024-9823
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThere 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceJetty's DosFilter (Denial of Service Filter) has a vulnerability where repeatedly sending crafted requests triggers OutofMemory errors, causing memory exhaustion and denial of service. The filter fails to properly limit or sanitize request handling, allowing attackers to consume excessive server memory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versions>= 9.0.0, < 9.4.54>= 10.0.0, < 10.0.18>= 11.0.0, < 11.0.18>= 12.0.0, < 12.0.3all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Jetty installation and versionLocate the Jetty server installation and check the version number in the distribution files, about page, or startup logs. Typical locations include the jetty-version.jar, VERSION.txt file, or server startup output.Affected if The installed Jetty version falls within the vulnerable ranges: 9.0.0 to 9.4.53, 10.0.0 to 10.0.17, 11.0.0 to 11.0.17, or 12.0.0 to 12.0.2.
-
Confirm DosFilter is in useSearch configuration files (web.xml, jetty.xml, or context deployment descriptors) for the DosFilter class org.eclipse.jetty.servlets.DoSFilter or any <filter> definition referencing DoSFilter.Affected if DosFilter is configured and active in the web application or server configuration.
-
Review DosFilter memory limits configurationLocate the DosFilter configuration in your XML files and inspect init-parameters such as maxRequestMs, maxIdleTime, or maxMemory. Check if maxMemoryMB, maxRequestSize, or throttlethreshold parameters are set to unreasonable or unlimited values.Affected if DosFilter lacks proper memory limits configuration, or limits are set such that a single request can consume unbounded memory (for example, maxMemoryMB is absent or set to a very high value).
-
Check Netapp product usageFor Netapp Active IQ Unified Manager or Bootstrap OS, determine if the embedded Jetty server is in use. Check product documentation or system information to confirm the Jetty version bundled with these Netapp products.Affected if Running any version of Netapp Active IQ Unified Manager or Bootstrap OS that includes the vulnerable Jetty DosFilter component.
You are affected if your environment uses Jetty (any version in the listed vulnerable ranges or Netapp products) and the DosFilter is enabled without proper memory/request limits configured, allowing unbounded memory allocation under crafted request load.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data9.4.5410.0.1811.0.18
Update Jetty to a version that includes the fix for this vulnerability, or if using DosFilter, review and properly configure its memory and request limits to prevent unbounded memory allocation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9823 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-9823 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data