Users outside an organization can delete a snapshot with its key

Summary

It is possible for a user in a different organization from the owner of a snapshot to bypass authorization and delete a snapshot by issuing a DELETE request to /api/snapshots/<key> using its view key. This functionality is intended to only be available to individuals with the permission to write/edit to the snapshot in question, but due to a bug in the authorization logic, deletion requests issued by an unprivileged user in a different organization than the snapshot owner are treated as authorized. Grafana Labs would like to thank Ravid Mazon and Jay Chen of Palo Alto Research for discovering and disclosing this vulnerability. This issue affects Grafana: from 9.5.0 before 9.5.18, from 10.0.0 before 10.0.13, from 10.1.0 before 10.1.9, from 10.2.0 before 10.2.6, from 10.3.0 before 10.3.5.

Timeline

1. Mar 26, 2024, 5:24 PM UTCCVE published
2. Jun 10, 2024, 8:46 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Feb 13, 2025, 5:27 PM UTCRecord last updated

Affected versions

• Grafana Grafana

  From 9.5.0 · fixed in 9.5.18; From 10.0.0 · fixed in 10.0.13; From 10.1.0 · fixed in 10.1.9; From 10.2.0 · fixed in 10.2.6; From 10.3.0 · fixed in 10.3.5

• github.com/grafana/grafanaGo

  From 9.5.0 · fixed in 9.5.18

• github.com/grafana/grafanaGo

  From 10.0.0 · fixed in 10.0.13

• github.com/grafana/grafanaGo

  From 10.1.0 · fixed in 10.1.9

• github.com/grafana/grafanaGo

  From 10.2.0 · fixed in 10.2.6

• github.com/grafana/grafanaGo

  From 10.3.0 · fixed in 10.3.5

• github.com/grafana/grafanaGo

  All versions

References 2