A user with read access to Grafana's server logs, or to a log store they are shipped to, can...
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Grafana | Grafana OSS |
≤ 12.3.11 ≥ 12.4.0, < 12.4.11 ≥ 13.0.0, < 13.0.9 ≥ 13.1.0, < 13.1.6 ≥ 13.2.0, < 13.2.2 |
— 12.4.11 13.0.9 13.1.6 13.2.2 |
| Grafana | Grafana Enterprise |
≤ 12.3.11 ≥ 12.4.0, < 12.4.11 ≥ 13.0.0, < 13.0.9 ≥ 13.1.0, < 13.1.6 ≥ 13.2.0, < 13.2.2 |
— 12.4.11 13.0.9 13.1.6 13.2.2 |
Original description The description as published by the source.
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.
Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory
References
- web security@grafana.com
- web nvd.nist.gov
- web github.com