Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-2842 medium CVSS 4.3

Information Disclosure in github.com/grafana/tempo-operator (CVE-2025-2842)

Summary

Vulnerability in github.com/grafana/tempo-operator (CVE-2025-2842). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.16.0 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-2842 has been found in github.com/grafana/tempo-operator.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade github.com/grafana/tempo-operator to 0.16.0 or later.
If unsure, ask your IT team or search "github.com/grafana/tempo-operator CVE-2025-2842" on the vendor's site.

CVE-2025-2842 (github.com/grafana/tempo-operator) — CWE-200 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.16.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in github.com/grafana/tempo-operator.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/grafana/tempo-operator.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.16.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/grafana/tempo-operator' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/grafana/tempo-operator' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/grafana/tempo-operator を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/grafana/tempo-operator to 0.16.0

    ステージング環境で 0.16.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/grafana/tempo-operator
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.16.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details