# CVE-2022-21673: OAuth Identity Token exposure in Grafana

> Attackers with API tokens can retrieve unauthorized data by exploiting OAuth identity forwarding in Grafana when specific features are enabled.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jan 2022
- **Updated:** 23 Apr 2025
- **Also known as:** BIT-grafana-2022-21673, GHSA-8wjh-59cw-9xh4, OESA-2022-1531, UBUNTU-CVE-2022-21673

## What is CVE-2022-21673?

CVE-2022-21673 is a medium-severity vulnerability in Fedoraproject Fedora, published on 18 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grafana is an open-source platform for monitoring and observability. In affected versions 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. This attack relies on the Grafana instance having data sources that support the Forward OAuth Identity feature, the Grafana instance having a data source with the Forward OAuth Identity feature toggled on, the Grafana instance having OAuth enabled, and the Grafana instance having usable API keys. This issue has been patched in versions 7.5.13 and 8.3.4.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-21673?

1 open source package ship an affected version, including grafana. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `grafana` | Bitnami | From 7.2.0 | 7.5.13, 8.3.4 |

Products: Fedoraproject Fedora, Grafana Grafana.

## How do I fix CVE-2022-21673?

Upgrade grafana to a fixed version for your release line: 7.5.13 or 8.3.4.

## Is CVE-2022-21673 being exploited?

There is no known exploitation of CVE-2022-21673 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-21673 and fix it if it is affected.

What it is: CVE-2022-21673 is a medium-severity vulnerability in Fedoraproject Fedora, published on 18 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-21673 in the wild and no public exploit code.

Affected packages and fixed versions:
- grafana (Bitnami): affected from 7.2.0; fixed in 7.5.13, 8.3.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-21673/ (Markdown: https://insights.sbomify.com/CVE-2022-21673/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-21673
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-21673
- OSV: https://osv.dev/vulnerability/CVE-2022-21673

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-21673/
Summaries are generated and may contain mistakes; the official description above is the record.