CyberSecBulletin
CVE-2025-9784NVD status: Modified

Red Hat build of Apache Camel 4.14.2 for…: Allocation of Resources Without Limits or Throttling

Published Updated By the CyberSecBulletin desk

CVE-2025-9784 is a high-severity allocation of resources without limits or throttling vulnerability in Red Hat build of Apache Camel 4.14.2 for Spring Boot 3.5.8 from Red Hat, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 2.33% chance of exploitation within 30 days, higher than 84% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of Red Hat build of Apache Camel 4.14.2 for Spring Boot 3.5.8 you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on access.redhat.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Red HatRed Hat build of Apache Camel 4.14.2 for Spring Boot 3.5.8Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.4.24Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 8Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 9Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.0Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.0 for RHEL 8Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.0 for RHEL 9Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.1.3Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.1 for RHEL 8Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.1 for RHEL 9Not specified in the recordNot stated
Red HatRed Hat Single Sign-On 7.6.13Not specified in the recordNot stated
Red HatRed Hat Single Sign-On 7.6 for RHEL 7Not specified in the recordNot stated
Red HatRed Hat Single Sign-On 7.6 for RHEL 8Not specified in the recordNot stated
Red HatRed Hat Single Sign-On 7.6 for RHEL 9Not specified in the recordNot stated
Red HatRHEL-8 based Middleware ContainersNot specified in the recordNot stated
Red HatRed Hat build of Apache Camel - HawtIO 4Not specified in the recordNot stated
Red HatRed Hat Data Grid 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatRed Hat Fuse 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE; 11 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (redhat.com).

Official description

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).

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Allocation of Resources Without Limits or Throttling

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How developers prevent this class of flaw

  • Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
  • Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

More Allocation of Resources Without Limits or Throttling vulnerabilities (CWE-770)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Allocation of Resources Without Limits or Throttling vulnerabilities

Spotted an error? Tell us.