Grafana OAuth token exposure in server logs
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 |
|
≥ 13.0.0 · < 13.0.9≥ 13.1.0 · < 13.1.6≥ 13.2.0 · < 13.2.2| No fix yet |
A user with read access to Grafana's server logs, or to a log store they are shipped to, can recover the OAuth and OIDC access, refresh and ID tokens of users who sign in through the Generic OAuth, Google or GitLab providers. Grafana writes these tokens to its logs unredacted when an access or ID token is not a valid JWT, when the ID token is missing (at debug level) or is not a string (exposure of sensitive information in log files). The exposure is bounded by the scopes granted to the configured OAuth client.
From the CVE record · GRAFANA
Grafana OSS and Enterprise can write OAuth and OIDC access, refresh, and ID tokens to server logs without redaction for users signing in through Generic OAuth, Google, or GitLab. This occurs when an access or ID token is not a valid JWT, when an ID token is missing at debug log level, or when an ID token is not a string. A person with read access to the logs or a log store receiving them can recover the tokens; exposure is limited to the configured OAuth client's granted scopes.
Teams running Grafana OSS or Grafana Enterprise with Generic OAuth, Google, or GitLab sign-in should check their installations; affected versions were not provided.