SmallRye smallrye-fault-tolerance improperly controlled sequential memory allocation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in SmallRye. The affected element is an unknown function of the component smallrye-fault-tolerance. The manipulation results in improperly controlled sequential memory allocation. This vulnerability is cataloged as CVE-2025-2240. There is no exploit available.
Details
A vulnerability, which was classified as problematic, was found in SmallRye (unknown version). Affected is an unknown code block of the component smallrye-fault-tolerance. The manipulation with an unknown input leads to a improperly controlled sequential memory allocation vulnerability. CWE is classifying the issue as CWE-1325. 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. This is going to have an impact on availability.
The advisory is available at bugzilla.redhat.com. This vulnerability is traded as CVE-2025-2240 since 03/12/2025. The exploitability is told to be easy. The technical details are unknown and an exploit is not available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-6307). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improperly controlled sequential memory allocationCWE: CWE-1325
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/12/2025 🔍03/12/2025 🔍
03/12/2025 🔍
06/12/2025 🔍
Sources
Advisory: bugzilla.redhat.comStatus: Not defined
CVE: CVE-2025-2240 (🔍)
GCVE (CVE): GCVE-0-2025-2240
GCVE (VulDB): GCVE-100-299514
EUVD: 🔍
Entry
Created: 03/12/2025 07:24Updated: 06/12/2025 03:12
Changes: 03/12/2025 07:24 (49), 06/12/2025 03:12 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.