CVE-2022-39324: Grafana Spoofing originalUrl of snapshots
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.
Published May 14, 2024 · Updated Aug 7, 2024
Affected packages
github.com/grafana/grafana
- Ecosystem
- Go
- Affected
- >= 9.0.0, < 9.2.8
- Fixed in
- 9.2.8
- Check
go list -m github.com/grafana/grafana
github.com/grafana/grafana
- Ecosystem
- Go
- Affected
- < 8.5.16
- Fixed in
- 8.5.16
- Check
go list -m github.com/grafana/grafana
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to r3kumar.
References
- https://github.com/grafana/grafana/security/advisories/GHSA-4724-7jwc-3fpw
- https://nvd.nist.gov/vuln/detail/CVE-2022-39324
- https://github.com/grafana/grafana/pull/60232
- https://github.com/grafana/grafana/pull/60256
- https://github.com/grafana/grafana/commit/239888f22983010576bb3a9135a7294e88c0c74a
- https://github.com/grafana/grafana/commit/d7dcea71ea763780dc286792a0afd560bff2985c
- https://github.com/advisories/GHSA-4724-7jwc-3fpw
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-10601
Grafana: Path traversal in the Tempo and Loki data source plugins
medium5.4No fixJun 22, 2026CVE-2026-42127
Grafana: Pre-authentication denial of service in the public dashboard query handler
high7.5No fixJun 22, 2026CVE-2026-42129
Grafana Loki datasource plugin's callResource handler contains a path traversal vulnerability.
high7.7No fixJun 22, 2026CVE-2026-9029
Grafana geomap panel's XYZ tile layer has a sanitize-then-interpolate ordering bug
high7.3No fixJun 22, 2026CVE-2026-33380
Grafana: SQL Expressions Read File From Disk
medium6.3May 13, 2026CVE-2026-33381
Grafana: Users can generate Service Account tokens after permissions removal
medium5.9May 13, 2026
