Editor can forge file-provisioning provenance on dashboards via the dashboard API
- 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, 13.1.7, 13.2.3
- 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 Editor can set file-provisioning metadata (the grafana.app/managedBy, grafana.app/managerId and grafana.app/sourcePath annotations) when creating a dashboard through the dashboard API, because these fields were stored without an authorization check. The dashboard then appears file-provisioned, and administrators can no longer update or delete it through Grafana. The impact is limited to the same organization and no data is exposed.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Grafana Grafana OSS
From 12.0.0 · through 12.0.10; 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; From 13.1.0 · fixed in 13.1.7; From 13.2.0 · fixed in 13.2.3
- Grafana Grafana Enterprise
From 12.0.0 · through 12.0.10; 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; From 13.1.0 · fixed in 13.1.7; From 13.2.0 · fixed in 13.2.3