Library panel can be moved into a folder without library panel create permission
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 12.4.12, 13.0.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
An authenticated user with edit permission on one folder can move a library panel into another folder where they only have view permission, through the library elements API or the equivalent App Platform resource. The update path did not check library panel create permission on the destination folder (incorrect authorization). No data from the destination folder is disclosed, and existing content there cannot be changed.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Grafana Grafana Enterprise
From 12.1.0 · through 12.1.10; From 12.2.0 · through 12.2.11; From 12.3.0 · through 12.3.11; From 12.4.0 · fixed in 12.4.12; From 13.0.0 · fixed in 13.0.10
- Grafana Grafana OSS
From 12.1.0 · through 12.1.10; From 12.2.0 · through 12.2.11; From 12.3.0 · through 12.3.11; From 12.4.0 · fixed in 12.4.12; From 13.0.0 · fixed in 13.0.10