Tempo-operator: tempo operator token exposition lead to read sensitive data
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| unaffected |
|
||||||||
| Red Hat | Red Hat OpenShift distributed tracing 3.5.3 | affected |
|
||||||
| Red Hat | Red Hat OpenShift distributed tracing 3.5.3 | affected |
|
||||||
| Red Hat | Red Hat OpenShift distributed tracing 3 | affected | — | ||||||
| Red Hat | Red Hat OpenShift distributed tracing 3 | affected | — | ||||||
| Red Hat | Red Hat OpenShift distributed tracing 3 | affected | — | ||||||
| Red Hat | Red Hat OpenShift distributed tracing 3 | affected | — | ||||||
| Red Hat | Red Hat OpenShift distributed tracing 3 | affected | — |
No data.
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift distributed tracing 3.5.1 | |||
| registry.redhat.io/rhosdt/tempo-rhel8-operator:sha256:a494025181bea65d1d839460a4a3985a46dc5f62cf7939b69293b95de5b1563a | cpe:/a:redhat:openshift_distributed_tracing:3.5::el8 | RHSA-2025:3607 | 2025-04-04T00:00:00Z |
| registry.redhat.io/rhosdt/tempo-rhel8-operator:sha256:d15d039fa5629a0a0c5abb6bced7aa635e9c5255913920232b02b1fb32c4e7fb | cpe:/a:redhat:openshift_distributed_tracing:3.5::el8 | RHSA-2025:3740 | 2025-04-09T00:00:00Z |
No data available yet.
Vendor Workaround
Currently, no mitigation is available for this vulnerability.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-9549 | 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. |
Github GHSA |
GHSA-5xf3-gmx4-529v | Grafana Tempo Operator Vulnerable to Exposure of Sensitive Information to an Unauthorized Actor |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.397% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:openshift_distributed_tracing:3.5::el8 | |
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Tempo-operator: tempo operator token exposition lead to read sensitive data | |
| First Time appeared |
Redhat
Redhat openshift Distributed Tracing |
|
| Weaknesses | CWE-200 | |
| CPEs | cpe:/a:redhat:openshift_distributed_tracing:3 | |
| Vendors & Products |
Redhat
Redhat openshift Distributed Tracing |
|
| References |
| |
| Metrics |
cvssV3_1
|