Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2024-1313

grafana: vulnerable to authorization bypass

Overview

Published
26 Mar 2024
Modified
17 Jun 2026
Medium CVE
2 Registry packages
8 OS packages
8 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Weakness: CWE-639

Affected packages · 2

Packages affected by CVE-2024-1313
EcosystemPackageVulnerableFixed in
Bitnami grafana >=9.5.0, <9.5.18>=10.0.0, <10.0.13>=10.1.0, <10.1.9>=10.2.0, <10.2.6>=10.3.0, <10.3.5 9.5.1810.0.1310.1.910.2.610.3.5
Go github.com/grafana/grafana >=9.5.0, <9.5.18>=10.0.0, <10.0.13>=10.1.0, <10.1.9>=10.2.0, <10.2.6>=10.3.0, <10.3.5 9.5.1810.0.1310.1.910.2.610.3.5

Open a package to see all its vulnerabilities.

Operating systems · 19 fixes

Oracle Linux 2 releases · 1 package

fixed 2
grafana
Oracle Linux fixes for CVE-2024-1313
ReleasePackageFixed in
8 grafana +1 9.2.10-16.el8_10
9 grafana +1 9.2.10-16.el9_4

Red Hat 3 releases · 1 package

eol 1 fixed 2
grafana
Red Hat fixes for CVE-2024-1313
ReleasePackageFixed inAdvisory
grafana eol —
8 grafana +1 0:9.2.10-16.el8_10 RHSA-2024:3265
9 grafana +1 0:9.2.10-16.el9_4 RHSA-2024:2568

SUSE Linux Enterprise 3 releases · 3 packages

fixed 4
golang-github-prometheus-node-exporter golang-github-prometheus-promu grafana
SUSE Linux Enterprise fixes for CVE-2024-1313
ReleasePackageFixed inAdvisory
12.5 golang-github-prometheus-node-exporter 1.7.0-1.30.2 SUSE-SU-2024:1508-1
15.5 golang-github-prometheus-promu 0.14.0-150000.3.18.2 SUSE-SU-2024:1509-1
15.5 grafana 9.5.18-150200.3.56.1 SUSE-SU-2024:1530-1
15.6 grafana 9.5.18-150200.3.56.1 SUSE-SU-2024:1530-2

alma 2 releases · 1 package

fixed 2
grafana
alma fixes for CVE-2024-1313
ReleasePackageFixed in
8 grafana +1 9.2.10-16.el8_10
9 grafana +1 9.2.10-16.el9_4.alma.1

chainguard 1 release · 4 packages

not affected 1 fixed 3
grafana-fips-11-6 grafana-fips-12-0 grafana-fips-12-1 grafana-fips-13-1
chainguard fixes for CVE-2024-1313
ReleasePackageFixed in
grafana-fips-11-6 +4 not affected
grafana-fips-12-0 12.0.10-r6
grafana-fips-12-1 12.1.10.01-r3
grafana-fips-13-1 13.1.0-r0

minimos 1 release · 1 package

fixed 1
grafana-11-4
minimos fixes for CVE-2024-1313
ReleasePackageFixed in
grafana-11-4 11.4.3-r0

openSUSE 1 release · 1 package

fixed 1
grafana
openSUSE fixes for CVE-2024-1313
ReleasePackageFixed inAdvisory
Tumbleweed grafana 10.3.5-1.1 openSUSE-SU-2024:13831-1

rocky 2 releases · 1 package

fixed 2
grafana
rocky fixes for CVE-2024-1313
ReleasePackageFixed in
8 grafana +1 9.2.10-16.el8_10
9 grafana +1 9.2.10-16.el9_4

References

Show all 23 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.