CVE-2025-2240: Improperly Controlled Sequential Memory Allocation
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.
AI Analysis
Technical Summary
CVE-2025-2240 identifies a vulnerability in the smallrye-fault-tolerance library used within Red Hat Build of Apache Camel 4.8 for Quarkus 3.15, affecting versions 6.3.0 and 6.5.0. The root cause is an improperly controlled sequential memory allocation triggered by external calls to the metrics URI endpoint. Each invocation of this URI results in the creation of a new object within the internal meterMap data structure without proper limits or cleanup, causing memory consumption to grow unbounded. Over time or under high request volumes, this leads to an out-of-memory (OOM) condition, which can crash or severely degrade the affected application, resulting in a denial of service (DoS). The vulnerability does not impact confidentiality or integrity but severely affects availability. It is remotely exploitable without authentication or user interaction, with low attack complexity, making it accessible to attackers who can send repeated requests to the metrics endpoint. The absence of known exploits in the wild suggests it is newly discovered, but the potential for automated exploitation exists given the nature of the flaw. The vulnerability was published on March 12, 2025, and is tracked under CVE-2025-2240 with a CVSS v3.1 score of 7.5 (high severity).
Potential Impact
The primary impact of CVE-2025-2240 is denial of service due to out-of-memory conditions triggered by repeated access to the metrics URI. Organizations running affected versions of Red Hat Build of Apache Camel for Quarkus may experience service outages or degraded performance, impacting business continuity and availability of critical applications. This can disrupt internal operations, customer-facing services, and automated workflows relying on these components. Since the vulnerability is remotely exploitable without authentication, attackers can easily target exposed endpoints to cause service disruptions. This risk is heightened in cloud environments, microservices architectures, and containerized deployments where Apache Camel and Quarkus are commonly used. The lack of impact on confidentiality or integrity limits data breach concerns, but the availability impact alone can result in significant operational and reputational damage. Additionally, the vulnerability could be leveraged as part of a larger attack chain to distract or exhaust resources during multi-vector attacks.
Mitigation Recommendations
To mitigate CVE-2025-2240, organizations should promptly upgrade to patched versions of Red Hat Build of Apache Camel for Quarkus once available. In the absence of immediate patches, implement network-level controls to restrict access to the metrics URI endpoint, such as IP whitelisting, firewall rules, or API gateway filtering. Rate limiting and throttling requests to the metrics endpoint can reduce the risk of memory exhaustion. Monitoring memory usage and application logs for unusual spikes related to meterMap growth can provide early detection of exploitation attempts. Consider disabling or restricting the metrics endpoint if it is not essential for operations. Additionally, conduct thorough testing of fault-tolerance and metrics components in staging environments to identify abnormal resource consumption. Collaborate with Red Hat support and subscribe to security advisories for updates. Finally, incorporate this vulnerability into incident response plans to quickly address potential DoS incidents.
Affected Countries
United States, Germany, India, United Kingdom, France, Japan, Canada, Australia, Brazil, Netherlands, South Korea, China, Singapore
CVE-2025-2240: Improperly Controlled Sequential Memory Allocation
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-2240 identifies a vulnerability in the smallrye-fault-tolerance library used within Red Hat Build of Apache Camel 4.8 for Quarkus 3.15, affecting versions 6.3.0 and 6.5.0. The root cause is an improperly controlled sequential memory allocation triggered by external calls to the metrics URI endpoint. Each invocation of this URI results in the creation of a new object within the internal meterMap data structure without proper limits or cleanup, causing memory consumption to grow unbounded. Over time or under high request volumes, this leads to an out-of-memory (OOM) condition, which can crash or severely degrade the affected application, resulting in a denial of service (DoS). The vulnerability does not impact confidentiality or integrity but severely affects availability. It is remotely exploitable without authentication or user interaction, with low attack complexity, making it accessible to attackers who can send repeated requests to the metrics endpoint. The absence of known exploits in the wild suggests it is newly discovered, but the potential for automated exploitation exists given the nature of the flaw. The vulnerability was published on March 12, 2025, and is tracked under CVE-2025-2240 with a CVSS v3.1 score of 7.5 (high severity).
Potential Impact
The primary impact of CVE-2025-2240 is denial of service due to out-of-memory conditions triggered by repeated access to the metrics URI. Organizations running affected versions of Red Hat Build of Apache Camel for Quarkus may experience service outages or degraded performance, impacting business continuity and availability of critical applications. This can disrupt internal operations, customer-facing services, and automated workflows relying on these components. Since the vulnerability is remotely exploitable without authentication, attackers can easily target exposed endpoints to cause service disruptions. This risk is heightened in cloud environments, microservices architectures, and containerized deployments where Apache Camel and Quarkus are commonly used. The lack of impact on confidentiality or integrity limits data breach concerns, but the availability impact alone can result in significant operational and reputational damage. Additionally, the vulnerability could be leveraged as part of a larger attack chain to distract or exhaust resources during multi-vector attacks.
Mitigation Recommendations
To mitigate CVE-2025-2240, organizations should promptly upgrade to patched versions of Red Hat Build of Apache Camel for Quarkus once available. In the absence of immediate patches, implement network-level controls to restrict access to the metrics URI endpoint, such as IP whitelisting, firewall rules, or API gateway filtering. Rate limiting and throttling requests to the metrics endpoint can reduce the risk of memory exhaustion. Monitoring memory usage and application logs for unusual spikes related to meterMap growth can provide early detection of exploitation attempts. Consider disabling or restricting the metrics endpoint if it is not essential for operations. Additionally, conduct thorough testing of fault-tolerance and metrics components in staging environments to identify abnormal resource consumption. Collaborate with Red Hat support and subscribe to security advisories for updates. Finally, incorporate this vulnerability into incident response plans to quickly address potential DoS incidents.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- redhat
- Date Reserved
- 2025-03-12T02:36:02.101Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d9816c4522896dcbd6c33
Added to database: 5/21/2025, 9:08:38 AM
Last enriched: 2/27/2026, 12:48:43 PM
Last updated: 3/26/2026, 8:45:47 AM
Views: 57
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.