CVE-2025-2842: Tempo-operator: tempo operator token exposition lead to read sensitive data
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.
Security readout for executives and security teams
Plain-English summary
A permissions flaw can let a namespace administrator or similarly privileged user turn a Tempo service-account token into access to cluster-wide monitoring metrics. It affects deployments where the Jaeger UI Monitor Tab is enabled and the Tempo Operator grants the service account the cluster-monitoring-view role. The disclosed impact is sensitive-data exposure, not modification or service disruption.
Executive priority
Prioritize affected shared or sensitive OpenShift clusters, especially where namespace administration is delegated broadly. Treat this as a moderate confidentiality issue: exploitation needs prior privileges, but exposed cluster metrics may reveal operationally sensitive information. Patch during the next controlled maintenance window, accelerating where the prerequisite permissions are widely assigned.
Technical view
The Tempo Operator creates a ClusterRoleBinding to cluster-monitoring-view when Jaeger UI monitoring is enabled. A user able to create TempoStack resources and read Secrets in that namespace can obtain the Tempo service-account token and use its resulting cluster-wide metrics access. The issue is classified as CWE-200 with CVSS 3.1 score 4.3.
Likely exposure
Exposure requires a Tempo Operator-managed instance with Jaeger UI Monitor Tab enabled, plus a user holding both TempoStack creation and Secret-read permissions in its namespace. The bundle identifies affected Red Hat OpenShift distributed tracing 3 and 3.5.2 components. Exact fixed-version boundaries are not provided.
Exploitation context
The attack requires existing authenticated namespace privileges; it is not described as unauthenticated compromise. The disclosed result is read access to cluster metrics. The source bundle marks the CVE as absent from KEV and provides no evidence of active exploitation.
Researcher notes
The stated vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. Validate the full authorization chain rather than token readability alone: feature enablement, generated ClusterRoleBinding, service-account credentials, and effective monitoring permissions. The bundle references an upstream pull request, but does not provide enough detail to state the exact code change or fixed upstream version.
Mitigation direction
Apply updates identified in the relevant Red Hat security advisories.
Check current Grafana Tempo Operator guidance for the corrected release.
Disable Jaeger UI Monitor Tab functionality where operationally acceptable until remediation.
Restrict TempoStack creation and Secret-read permissions to trusted administrators.
Review unnecessary cluster-monitoring-view bindings created for Tempo service accounts.
Validation and detection
Inventory Tempo Operator and Red Hat OpenShift distributed tracing versions.
Identify TempoStack instances with Jaeger UI Monitor Tab enabled.
Inspect Tempo service-account bindings to the cluster-monitoring-view role.
Audit namespace roles combining TempoStack creation with Secret-read access.
Confirm installed packages match vendor-remediated versions in applicable advisories.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-200 · source CWE mapping
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.