# CVE-2023-2801: Grafana Missing Synchronization vulnerability

> Attackers can crash Grafana instances by exploiting mixed queries in public dashboards or the query API, requiring an upgrade to patched versions.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jun 2023
- **Updated:** 13 Feb 2025
- **Also known as:** BIT-grafana-2023-2801, GHSA-x2w4-c67p-g44j, UBUNTU-CVE-2023-2801

## What is CVE-2023-2801?

CVE-2023-2801 is a high-severity denial of service vulnerability in Grafana Grafana, published on 6 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Grafana is an open-source platform for monitoring and observability. 

Using public dashboards users can query multiple distinct data sources using mixed queries. However such query has a possibility of crashing a Grafana instance.

The only feature that uses mixed queries at the moment is public dashboards, but it's also possible to cause this by calling the query API directly.

This might enable malicious users to crash Grafana instances through that endpoint.

Users may upgrade to version 9.4.12 and 9.5.3 to receive a fix.

Weakness: CWE-662 (Improper Synchronization), CWE-820 (Missing Synchronization)

## Which versions are affected by CVE-2023-2801?

5 open source packages ship an affected version, including github.com/grafana/grafana and grafana. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/grafana/grafana` | Go | All versions | 9.4.12 |
| `github.com/grafana/grafana` | Go | All versions | 9.4.12 |
| `github.com/grafana/grafana` | Go | From 9.5.0 | 9.5.3 |
| `github.com/grafana/grafana` | Go | From 9.5.0 | 9.5.3 |
| `grafana` | Bitnami | From 9.4.0 | 9.4.12, 9.5.3 |

Products: Grafana Grafana.

## How do I fix CVE-2023-2801?

Upgrade github.com/grafana/grafana to a fixed version for your release line: 9.4.12 or 9.5.3.

## Is CVE-2023-2801 being exploited?

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

## Other vulnerabilities in Grafana Grafana

- [CVE-2021-43798](https://insights.sbomify.com/CVE-2021-43798/): Grafana Path Traversal (high 7.5, exploited in the wild)
- [CVE-2025-41115](https://insights.sbomify.com/CVE-2025-41115/): Incorrect privilege assignment (critical 10.0)
- [CVE-2022-39328](https://insights.sbomify.com/CVE-2022-39328/): Grafana vulnerable to race condition allowing privilege escalation (critical 9.8)
- [CVE-2022-28660](https://insights.sbomify.com/CVE-2022-28660/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-26148](https://insights.sbomify.com/CVE-2022-26148/): Information disclosure in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2801 and fix it if it is affected.

What it is: CVE-2023-2801 is a high-severity denial of service vulnerability in Grafana Grafana, published on 6 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-2801 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/grafana/grafana (Go): affected all versions; fixed in 9.4.12
- github.com/grafana/grafana (Go): affected all versions; fixed in 9.4.12
- github.com/grafana/grafana (Go): affected from 9.5.0; fixed in 9.5.3
- github.com/grafana/grafana (Go): affected from 9.5.0; fixed in 9.5.3
- grafana (Bitnami): affected from 9.4.0; fixed in 9.4.12, 9.5.3

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-2023-2801/ (Markdown: https://insights.sbomify.com/CVE-2023-2801/index.md)
```

## Sources

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

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