Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy.
Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18).
Weakness
The product does not properly control the allocation and maintenance of a limited resource.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Multicluster Global Hub 1.3.4 | RedHat | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779212259 | * |
| Multicluster Global Hub 1.4.5 | RedHat | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779579439 | * |
| Multicluster Global Hub 1.5.4 | RedHat | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1778867753 | * |
| Multicluster Global Hub 1.6.2 | RedHat | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1780167118 | * |
| Multicluster Global Hub 1.7.1 | RedHat | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779925273 | * |
Potential Mitigations
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/147.html
- https://cwe.mitre.org/data/definitions/227.html
- https://cwe.mitre.org/data/definitions/492.html