Tempo-operator: serviceaccount token exposure leading to token and subject access reviews in openshift tempo operator
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:cbe0df797c34aebfec911c281fbfee9fe7713a4c45d778ae480cd6a7bcab202e | 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:e0e3273eceb8339638f2f1d91bb5eb6a57cfc0bc1442fcdea5fcff36812ccb4c | 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-9524 | A flaw was found in Tempo Operator, where it creates a ServiceAccount, ClusterRole, and ClusterRoleBinding when a user deploys a TempoStack or TempoMonolithic instance. This flaw allows a user with full access to their namespace to extract the ServiceAccount token and use it to submit TokenReview and SubjectAccessReview requests, potentially revealing information about other users' permissions. While this does not allow privilege escalation or impersonation, it exposes information that could aid in gathering information for further attacks. |
Github GHSA |
GHSA-28gr-56hr-prp6 | 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.376% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:openshift_distributed_tracing:3.5::el8 | |
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in Tempo Operator, where it creates a ServiceAccount, ClusterRole, and ClusterRoleBinding when a user deploys a TempoStack or TempoMonolithic instance. This flaw allows a user with full access to their namespace to extract the ServiceAccount token and use it to submit TokenReview and SubjectAccessReview requests, potentially revealing information about other users' permissions. While this does not allow privilege escalation or impersonation, it exposes information that could aid in gathering information for further attacks. | |
| Title | Tempo-operator: serviceaccount token exposure leading to token and subject access reviews in openshift tempo operator | |
| 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
|