OAuth and OIDC tokens written unredacted to server logs by the Generic OAuth, Google and GitLab connectors
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 12.4.11, 13.0.9, 13.1.6, 13.2.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Grafana's Generic OAuth, Google, and GitLab sign-in connectors are affected. Under certain conditions they write users' OAuth and OIDC access, refresh, and ID tokens to server logs without redaction, so anyone who can read those logs, or the log store they are sent to, could obtain those tokens.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Grafana Grafana OSS
through 12.3.11; From 12.4.0 · fixed in 12.4.11; From 13.0.0 · fixed in 13.0.9; From 13.1.0 · fixed in 13.1.6; From 13.2.0 · fixed in 13.2.2
- Grafana Grafana Enterprise
through 12.3.11; From 12.4.0 · fixed in 12.4.11; From 13.0.0 · fixed in 13.0.9; From 13.1.0 · fixed in 13.1.6; From 13.2.0 · fixed in 13.2.2