Grafana cross-instance user impersonation in image renderer authentication
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.4.0 · ≤ 12.4.14≥ 13.0.0 · ≤ 13.0.12≥ 13.1.0 · ≤ 13.1.9≥ 13.2.0 · ≤ 13.2.5≥ 13.3.0 · ≤ 13.3.0| No fix yet |
When independent Grafana instances share the same [rendering] renderer_token, an image renderer key issued by one instance is accepted by the others, so a user on one instance could act as the user with the same ID on another (origin validation error). This affects instances with the renderAuthJWT feature toggle enabled, the default from Grafana 13.0.0.
From the CVE record · GRAFANA
When independent Grafana instances share the same renderer_token, an image renderer key issued by one instance is accepted by the others. A user on one instance could act as the user with the same ID on another. This requires the renderAuthJWT feature toggle to be enabled, which is the default from Grafana 13.0.0.
Operators of Grafana OSS or Grafana Enterprise instances sharing a renderer_token should check whether renderAuthJWT is enabled; it is enabled by default from version 13.0.0.