Tempo-operator: tempo operator token exposition lead to read sensitive data
tempo-operator · Red Hat OpenShift distributed tracing 3.5.3 · Red Hat OpenShift distributed tracing 3
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/grafana/tempo-operator Go |
|
|
Original description
A flaw was found in the Tempo Operator. When the Jaeger UI Monitor Tab functionality is enabled in a Tempo instance managed by the Tempo Operator, the Operator creates a ClusterRoleBinding for the Service Account of the Tempo instance to grant the cluster-monitoring-view ClusterRole. This can be exploited if a user has 'create' permissions on TempoStack and 'get' permissions on Secret in a namespace (for example, a user has ClusterAdmin permissions for a specific namespace), as the user can read the token of the Tempo service account and therefore has access to see all cluster metrics.
From the CVE record · redhat