MediumGHSA-4724-7jwc-3fpwBIT-grafana-2022-39324CVE-2022-39324GO-2024-2867

Grafana Spoofing originalUrl of snapshots

Published 14 May 2024 · Updated 10 Sept 2026

Is your project on an affected github.com/grafana/grafana?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=9.0.0 <9.2.8
Fixed in
9.2.8
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v9.2.8
Affected
<8.5.16
Fixed in
8.5.16
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v8.5.16

Details

To create a snapshot (and insert an arbitrary URL) the built-in role Viewer is sufficient. When a dashboard is shared as a local snapshot, the following three fields are offered in the web UI for a user to fill out: • Snapshotname • Expire • Timeout(seconds) After the user confirms creation of the snapshot (i.e. clicks the ”Local Snapshot” button) an HTTP POST request is sent to the Grafana server. The HTTP request contains additional parameters that are not visible in the web UI. The parameter originalUrl is not visible in the web UI, but sent in the HTTP POST request.

The value of the originalUrl parameter is automatically generated. The purpose of the presented originalUrl parameter is to provide a user that views the snapshot the possibility to click on the button in the Grafana web UI and be presented with the dashboard that the snapshot was made out of.

The value of the originalUrl parameter can be arbitrarily chosen by a malicious user that creates the snapshot (Note: by editing the query thanks to a web proxy like Burp) When another user opens the URL of the snapshot, they will be presented with the regular web interface delivered by the trusted Grafana server. The issue here is that the ”Open original dashboard” button no longer points to the to the real original dashboard but to the attacker’s (injected) URL.

Is GHSA-4724-7jwc-3fpw in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/grafana/grafana, and gives you the command that fixes it.

More advisories for github.com/grafana/grafana

  • LowCVE-2026-21727Grafana legacy correlations allow cross-tenant disclosure and deletion in github.com/grafana/grafana · 7 Oct 2026
  • LowCVE-2026-42127Grafana: Pre-authentication denial of service in the public dashboard query handler in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-9029Grafana geomap panel's XYZ tile layer has a sanitize-then-interpolate ordering bug in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-42129Grafana Loki datasource plugin's callResource handler contains a path traversal vulnerability. in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-10601Grafana: Path traversal in the Tempo and Loki data source plugins in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-33381Grafana: Users can generate Service Account tokens after permissions removal in github.com/grafana/grafana · 25 Jun 2026
All 112 advisories for github.com/grafana/grafana

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.