Tempo query limit results in unbounded memory allocation
Grafana Tempo · Grafana Enterprise Traces (GET)
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/grafana/tempo Go |
|
|
Grafana Tempo · Grafana Enterprise Traces (GET)
| Product | Affected | Fixed in |
|---|---|---|
| github.com/grafana/tempo Go |
|
|
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). Alternatively, automatically restart the service.
From the CVE record · GRAFANA
Tempo queries with large limits can trigger large memory allocations and affect service availability, depending on the deployment strategy. Someone able to submit such queries could cause this impact; the input does not specify whether authentication or user interaction is required.
Operators of Grafana Tempo or Grafana Enterprise Traces (GET) should check deployments using github.com/grafana/tempo versions >=1.3.0 <2.8.4, >=2.9.0 <2.9.2, or >=2.10.0 <2.10.2.