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.
Weakness
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.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat build of Apache Camel 4.8.5 for Spring Boot | RedHat | io.smallrye/smallrye-fault-tolerance-core | * |
| Red Hat Build of Apache Camel 4.8 for Quarkus 3.15 | RedHat | com.redhat.quarkus.platform/quarkus-camel-bom | * |
| Red Hat Build of Apache Camel 4.8 for Quarkus 3.15 | RedHat | com.redhat.quarkus.platform/quarkus-cxf-bom | * |
| Red Hat build of Quarkus 3.15.4 | RedHat | io.smallrye/smallrye-fault-tolerance-core | * |
Extended Description
While the product might limit the amount of memory that is allocated in a single operation for a single object (such as a malloc of an array), if an attacker can cause multiple objects to be allocated in separate operations, then this might cause higher total memory consumption than the developer intended, leading to a denial of service.