Editor can forge file-provisioning provenance on dashboards via the dashboard API
Grafana OSS · Grafana Enterprise
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Grafana Grafana OSS |
| No fix yet |
| Grafana Grafana Enterprise |
|
Grafana OSS · Grafana Enterprise
| Product | Affected | Fixed in |
|---|---|---|
| Grafana Grafana OSS |
| No fix yet |
| Grafana Grafana Enterprise |
|
≥ 12.1.0 · ≤ 12.1.10≥ 12.2.0 · ≤ 12.2.11≥ 12.3.0 · ≤ 12.3.11≥ 12.4.0 · < 12.4.12≥ 13.0.0 · < 13.0.10| No fix yet |
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.
From the CVE record · GRAFANA
Grafana OSS and Grafana Enterprise store file-provisioning metadata set by an Editor through the dashboard API without an authorization check. An authenticated Editor can create a dashboard that appears file-provisioned, preventing administrators from updating or deleting it through Grafana. The impact is limited to the same organization, and no data is exposed.
Teams running Grafana OSS or Grafana Enterprise should check their deployments; affected versions were not specified.