Sigstore Timestamp Authority: OOM due to unbounded metric label cardinality
sigstore timestamp-authority
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/sigstore/timestamp-authority/v2 Go |
|
|
| github.com/sigstore/timestamp-authority Go |
| No fix yet |
sigstore timestamp-authority
| Product | Affected | Fixed in |
|---|---|---|
| github.com/sigstore/timestamp-authority/v2 Go |
|
|
| github.com/sigstore/timestamp-authority Go |
| No fix yet |
Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.1.0, the global wrapMetrics middleware records raw HTTP request path r.URL.Path and raw HTTP request method r.Method as Prometheus labels for latency and request count metric vectors before routing, allowing an unauthenticated remote attacker to issue requests with random paths such as /api/v1/timestamp/<uuid> or random HTTP methods and create unbounded permanent time-series entries that exhaust memory. This issue is fixed in version 2.1.0.
From the CVE record · GitHub_M
The metrics middleware records raw HTTP paths and methods as Prometheus labels before routing requests. An unauthenticated remote attacker can send requests with random paths or methods to create unbounded, permanent time series that exhaust memory; no user interaction is needed.
Teams running Go package github.com/sigstore/timestamp-authority/v2 below 2.1.0 or github.com/sigstore/timestamp-authority at version 1.2.9 or earlier should check their deployments.