Headline
GHSA-mh7p-8m2f-qrm6: Grafana vulnerable to authorization bypass
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.
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2024-1313
Grafana vulnerable to authorization bypass
Moderate severity GitHub Reviewed Published Mar 26, 2024 to the GitHub Advisory Database • Updated Mar 27, 2024
Package
gomod github.com/grafana/grafana (Go)
Affected versions
>= 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
Patched versions
9.5.18
10.0.13
10.1.9
10.2.6
10.3.5
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.
References
- https://nvd.nist.gov/vuln/detail/CVE-2024-1313
- https://grafana.com/security/security-advisories/cve-2024-1313
Published to the GitHub Advisory Database
Mar 26, 2024
Last updated
Mar 27, 2024
Related news
### Summary The ***DELETE /api/snapshots/{key}*** endpoint allows any Grafana user to delete snapshots if the user is NOT in the organization of the snapshot ### Details An attacker (a user without organization affiliation or with a "no basic role" in an organization other than the one where the dashboard exists), knowing the key or URL of a snapshot created by any user (including Grafana admins), can delete a snapshot (It is not feasible using UI), resulting in a BOLA vulnerability. If an attacker is in the same organization of the dashboard snapshot, he can’t delete the snapshot. However, an attacker with low-privilege from a different organization would be able to delete it, resulting in the authorization flaw. ![Screenshot 2024-01-19 at 3 50 23 PM](https://user-images.githubusercontent.com/58054904/298194695-bea8ab57-8504-4f5d-9468-cef7acf8622b.png) ### Precondition To exploit this endpoint, an attacker must know the {key} of a snapshot. The attacker can potentially discover ...