dbcve.org
GrafanaApplication

CVE-2023-0594

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-01
Fix available
A fix is available. Upgrade to 8.5.21 / 9.2.13 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Grafana is an open-source platform for monitoring and observability. Starting with the 7.0 branch, Grafana had a stored XSS vulnerability in the trace view visualization. The stored XSS vulnerability was possible due the value of a span's attributes/resources were not properly sanitized and this will be rendered when the span's attributes/resources are expanded. An attacker needs to have the Editor role in order to change the value of a trace view visualization to contain JavaScript. This means that vertical privilege escalation is possible, where a user with Editor role can change to a known password for a user having Admin role if the user with Admin role executes malicious JavaScript viewing a dashboard. Users may upgrade to version 8.5.21, 9.2.13 and 9.3.8 to receive a fix.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stored XSS vulnerability in Grafana's trace view visualization where span attributes/resources are not properly sanitized, allowing injection of malicious JavaScript. An authenticated user with Editor role can inject JavaScript that executes when an Admin user views the affected trace view, enabling vertical privilege escalation.

MitigationUpgrade Grafana to version 8.5.21, 9.2.13, or 9.3.8 to receive the fix. Alternatively, implement input validation on span attributes before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GrafanaApplication
Affected:>= 7.0.0, < 8.5.21>= 9.2.0, < 9.2.13>= 9.3.0, < 9.3.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Grafana version
    Run 'grafana-server -v' or 'grafana-cli --version', or inspect the UI at Help > About. If running as a container, check the image tag. Compare the version number against the affected ranges: 7.0.0 to 8.5.20, 9.2.0 to 9.2.12, or 9.3.0 to 9.3.7.
    Affected if The installed version falls within any of the three affected ranges (7.0.0-8.5.20, 9.2.0-9.2.12, or 9.3.0-9.3.7).
  2. Verify tracing or Tempo data source is configured
    Navigate to Configuration > Data Sources in the Grafana UI, or query the data sources API endpoint. Look for Grafana Tempo, Jaeger, Zipkin, or other tracing data sources.
    Affected if A tracing data source (Tempo, Jaeger, Zipkin) is configured and active.
  3. Confirm trace view functionality is in use
    Check Grafana explore view or dashboards for any panels or links that open trace visualization. Inspect recent query logs or access logs for '/api/v3/traces/' or similar trace viewer endpoints.
    Affected if Users have accessed trace view visualizations within the timeframe the vulnerability could be exploited.
  4. Review user role assignments
    Query the Grafana user API or inspect Organization > Users to identify users with Editor and Admin roles. The attack requires an Editor to inject and an Admin to trigger the XSS.
    Affected if Both Editor role and Admin role users exist in the Grafana instance.

You are affected if your Grafana version is within the affected ranges AND you have a tracing data source configured with trace view accessible to both Editor and Admin role users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.5.21 / 9.2.13 / 9.3.8 or later
Fixed in 8.5.219.2.139.3.8
Interim mitigation

Upgrade Grafana to version 8.5.21, 9.2.13, or 9.3.8 to receive the fix. Alternatively, implement input validation on span attributes before rendering.

Recommended fix High confidence

8.5.21, 9.2.13, or 9.3.8 (depending on your current major version branch)

  1. Identify your current Grafana version by checking the grafana-server version or configuration
  2. If running version 7.0.0 to 7.x, upgrade to 8.5.21 (or preferably to a newer 8.x LTS release)
  3. If running version 9.2.0 to 9.2.x, upgrade to 9.2.13
  4. If running version 9.3.0 to 9.3.x, upgrade to 9.3.8
  5. After upgrading, verify the trace view visualization functionality works correctly
  6. Ensure the Grafana service is restarted after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grafana Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0594 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-0594 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data