Red Hat build of Apache Camel 4.8.5 for Spring…: Improperly Controlled Sequential Memory Allocation
CVE-2025-2240 is a high-severity improperly controlled sequential memory allocation vulnerability in Red Hat build of Apache Camel 4.8.5 for Spring Boot 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 1.23% chance of exploitation within 30 days, higher than 69% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Red Hat build of Apache Camel 4.8.5 for Spring Boot you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | Red Hat build of Apache Camel 4.8.5 for Spring Boot | Not specified in the record | Not stated |
| Red Hat | Red Hat Build of Apache Camel 4.8 for Quarkus 3.15 | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Quarkus 3.15.4 | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Apicurio Registry 2 | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Apicurio Registry 3 | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Quarkus | Not specified in the record | Not stated |
| Red Hat | Red Hat Fuse 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat Integration Camel K 1 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform Expansion Pack | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. 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 Smallrye, where smallrye-fault-tolerance is vulnerable to an out-of-memory (OOM) issue. This vulnerability is externally triggered when calling the metrics URI. Every call creates a new object within meterMap and may lead to a denial of service (DoS) issue.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improperly Controlled Sequential Memory Allocation
The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.
How developers prevent this class of flaw
- Ensure multiple allocations of the same kind of object are properly tracked - possibly across multiple sessions, requests, or messages. Define an appropriate strategy for handling requests that exceed the limit, and consider supporting a configuration option so that the administrator can extend the amount of memory to be used if necessary.
- Run the program using system-provided resource limits for memory. This might still cause the program to crash or exit, but the impact to the rest of the system will be minimized.
More Improperly Controlled Sequential Memory Allocation vulnerabilities (CWE-1325)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Recent Improperly Controlled Sequential Memory Allocation vulnerabilities
- 7.8 High severity
Spotted an error? Tell us.