CVE-2022-21673

When a data source has the Forward OAuth Identity feature enabled, sending a query to that datasource with an API token (and no other user credentials) will forward the OAuth Identity of the most recently logged-in user.

This can allow API token holders to retrieve data for which they may not have intended access.

Workarounds

Administrators of Grafana instances can limit the availability of API tokens.

Reporting security issues

If you think you have found a security vulnerability, please send a report to [email protected]. This address can be used for all of Grafana Labs' open source and commercial products (including, but not limited to Grafana, Grafana Cloud, Grafana Enterprise, and grafana.com). We can accept only vulnerability reports at this address. We would prefer that you encrypt your message to us by using our PGP key. The key fingerprint is

F988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA

The key is available from keyserver.ubuntu.com.

Security announcements

We maintain a security category on our blog, where we will always post a summary, remediation, and mitigation details for any patch containing security fixes.

You can also subscribe to our RSS feed.

All of the following must be true:

• The Grafana instance has data sources that support the Forward OAuth Identity feature. Graphite users, for example.
  • Some data sources are not susceptible, like Prometheus, as they do not have support for this feature.
  • The option being available is not sufficient enough to determine if the data source is susceptible.
• The Grafana instance has a data source with the Forward OAuth Identity feature toggled on.
• The Grafana instance has OAuth enabled.
• The Grafana instance has usable API keys.

CVE-2022-21673 has a CVSS score of 2.2 (Low). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.5.13, 8.3.4); upgrading removes the vulnerable code path.

Kodem intelligence

The following Grafana versions have been patched:

• v8.3.4
• v7.5.13

1. What is CVE-2022-21673? CVE-2022-21673 is a low-severity security vulnerability in github.com/grafana/grafana (go), affecting versions > 7.2.0, < 7.5.13. It is fixed in 7.5.13, 8.3.4.
2. How severe is CVE-2022-21673? CVE-2022-21673 has a CVSS score of 2.2 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/grafana/grafana are affected by CVE-2022-21673? github.com/grafana/grafana (go) versions > 7.2.0, < 7.5.13 is affected.
4. Is there a fix for CVE-2022-21673? Yes. CVE-2022-21673 is fixed in 7.5.13, 8.3.4. Upgrade to this version or later.
5. Is CVE-2022-21673 exploitable, and should I be worried? Whether CVE-2022-21673 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-21673 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-21673?
   • Upgrade github.com/grafana/grafana to 7.5.13 or later
   • Upgrade github.com/grafana/grafana to 8.3.4 or later