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.

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.

grafana-12.4.11-1.1 on GA media

grafana: OAuth and OIDC tokens written unredacted to Grafana server logs fast-uri: fast-uri: Path traversal via improper relative URI normalization fast-uri: fast-uri: Security policy bypass via improper host canonicalization fast-uri: fast-uri: Cross-Site Scripting via improper URI scheme decoding fast-uri: fast-uri: Cross-site scripting via unescaped colon in relative URI paths body-parser: body-parser: Denial of Service via unhandled decompression stream error