Prometheus: remote read endpoint allows denial of service via crafted snappy payload
prometheus
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/prometheus/prometheus Go |
|
|
| github.com/prometheus/prometheus/v2 Go |
prometheus
| Product | Affected | Fixed in |
|---|---|---|
| github.com/prometheus/prometheus Go |
|
|
| github.com/prometheus/prometheus/v2 Go |
all versions| No fix yet |
Prometheus is an open-source monitoring system and time series database. Prior to versions 3.5.3 and 3.11.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. This issue has been patched in versions 3.5.3 and 3.11.3.
From the CVE record · GitHub_M
The Prometheus remote read endpoint does not validate the declared decoded length of a snappy-compressed request before allocating memory. An unauthenticated attacker can send a small request that triggers a large allocation; concurrent requests can exhaust memory and crash the process.
Operators running Prometheus before 3.5.3 or 3.11.3, and users of the affected Go packages github.com/prometheus/prometheus and github.com/prometheus/prometheus/v2, should check their versions.