Build Of Apache Camel For Spring BootWeb server / proxy · Redhat

CVE-2025-9784

HIGH · 7.5 CVSS v3.1 Published 2025-09-02
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

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 · unedited
A flaw was found in Undertow where malformed client requests can trigger server-side stream resets without triggering abuse counters. This issue, referred to as the "MadeYouReset" attack, allows malicious clients to induce excessive server workload by repeatedly causing server-side stream aborts. While not a protocol bug, this highlights a common implementation weakness that can be exploited to cause a denial of service (DoS).

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
How this class of weakness works · CWE-770

The application allocates memory, connections, or handles in response to a request without enforcing any cap, so a modest amount of malicious traffic exhausts the resource and denies service to everyone else. The fix is enforcing quotas, limits, and timeouts on what any single request or client can consume.

General guidance for the resource allocation without limits class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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 data
Build Of Apache Camel For Spring BootWeb server / proxy
Affected:all versions
FuseApplication
Affected:= 7.0.0
Jboss Enterprise Application PlatformApplication
Affected:= 7.0.0= 8.0.0
Jboss Enterprise Application Platform Expansion PackApplication
Affected:all versions
Process AutomationApplication
Affected:= 7.0
Single Sign OnApplication
Affected:= 7.0
UndertowApplication
Affected:all versions
Enterprise LinuxOperating system
Affected:= 8.0= 9.0

CVSS 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

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Recommended fix Moderate confidence

Upgrade to the Undertow version that incorporates the fix from https://github.com/undertow-io/undertow/pull/1778. For Red Hat JBoss/WildFly based products, apply the corresponding security errata for CVE-2025-9784

  1. Identify the Undertow version currently in use by checking project dependencies (e.g., Maven pom.xml, Gradle build.gradle, or application package manifest)
  2. Upgrade Undertow to the version containing the fix from PR #1778. For Red Hat products, apply the corresponding security advisory/errata that addresses CVE-2025-9784
  3. After upgrading Undertow, rebuild and redeploy the application
  4. Restart the affected services to ensure the new Undertow version is loaded
  5. Verify the fix is applied by confirming the Undertow version includes the stream reset abuse prevention changes
  6. Test that normal request/response flows continue to work correctly after the upgrade
Caveat Undertow version upgrades may introduce compatibility changes; review release notes for any breaking changes related to HTTP/2 stream handling and servlet container behavior

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9784 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9784 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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