| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/prometheus/prometheus | ≥ 0.306.0, < 0.311.3≥ 1.0.0-rc.0, ≤ 2.5.0≥ 1.0.0-rc.0< 0.305.2 | 0.311.30.305.2 |
| github.com/prometheus/prometheus/v2 | all versions | |
| prometheus | ≥ 3.6.0, < 3.11.3< 3.5.3 | 3.11.33.5.3 |
The remote read endpoint (/api/v1/read) does not validate the declared decoded length in a snappy-compressed request body before allocating memory.
An unauthenticated attacker can send a small payload that causes a huge heap allocation per request. Under concurrent load this can exhaust available memory and crash the Prometheus process.
Has the problem been patched? What versions should users upgrade to?
Fixed in 3.11.3 and 3.5.3 LTS. Users should upgrade to these versions or later.
User who can not upgrade can place Prometheus behind a reverse proxy or firewall that requires authentication before requests reach /api/v1/read.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free