# CVE-2023-3128: Grafana vulnerable to Authentication Bypass by Spoofing > Attackers can bypass authentication and take over accounts in Grafana when Azure AD OAuth is configured with a multi-tenant application. - **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Jun 2023 - **Updated:** 13 Feb 2025 - **Also known as:** ALSA-2023:4030, ALSA-2023:6972, BIT-grafana-2023-3128, GHSA-gxh2-6vvc-rrgp, GHSA-mpv3-g8m3-3fjc, RHSA-2023:4030, RLSA-2023:4030, UBUNTU-CVE-2023-3128, openSUSE-SU-2024:13018-1 ## What is CVE-2023-3128? CVE-2023-3128 is a critical authentication bypass vulnerability in Grafana Grafana, published on 22 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Grafana is validating Azure AD accounts based on the email claim. On Azure AD, the profile email field is not unique and can be easily modified. This leads to account takeover and authentication bypass when Azure AD OAuth is configured with a multi-tenant app. Weakness: CWE-290 (Authentication Bypass by Spoofing) ## Which versions are affected by CVE-2023-3128? 9 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 | 8.5.27 | | `github.com/grafana/grafana` | Go | All versions | 8.5.27 | | `github.com/grafana/grafana` | Go | From 9.0.0 | 9.2.20 | | `github.com/grafana/grafana` | Go | From 9.0.0 | 9.2.20 | | `github.com/grafana/grafana` | Go | From 9.3.0 | 9.3.16 | | `github.com/grafana/grafana` | Go | From 9.3.0 | 9.3.16 | | `github.com/grafana/grafana` | Go | From 9.4.0 | 9.4.13 | | `github.com/grafana/grafana` | Go | From 9.4.0 | 9.4.13 | | `grafana` | Bitnami | From 6.7.0 | 8.5.27, 9.2.20, 9.3.16, 9.4.13, 9.5.4 | | `grafana` | AlmaLinux:8 | All versions | 9.2.10-7.el8_9.alma.1 | | `grafana` | AlmaLinux:9 | All versions | 9.0.9-3.el9_2.alma | | `grafana` | Red Hat:enterprise_linux:9::appstream | All versions | 0:9.0.9-3.el9_2 | | `grafana-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:9.0.9-3.el9_2 | | `grafana-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:9.0.9-3.el9_2 | | `grafana` | Rocky Linux:9 | All versions | 0:9.0.9-3.el9_2 | | `grafana` | openSUSE:Tumbleweed | All versions | 10.0.1-1.1 | Products: Grafana Grafana. ## How do I fix CVE-2023-3128? Upgrade github.com/grafana/grafana to a fixed version for your release line: 8.5.27, 9.2.20, 9.3.16 or 9.4.13. ## Is CVE-2023-3128 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3128 exists. Public exploit code: - https://github.com/spyata123/CVE-2023-3128 (github_poc): https://github.com/spyata123/CVE-2023-3128 ## 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-3128 and fix it if it is affected. What it is: CVE-2023-3128 is a critical authentication bypass vulnerability in Grafana Grafana, published on 22 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3128 exists. Affected packages and fixed versions: - github.com/grafana/grafana (Go): affected all versions; fixed in 8.5.27 - github.com/grafana/grafana (Go): affected all versions; fixed in 8.5.27 - github.com/grafana/grafana (Go): affected from 9.0.0; fixed in 9.2.20 - github.com/grafana/grafana (Go): affected from 9.0.0; fixed in 9.2.20 - github.com/grafana/grafana (Go): affected from 9.3.0; fixed in 9.3.16 - github.com/grafana/grafana (Go): affected from 9.3.0; fixed in 9.3.16 - github.com/grafana/grafana (Go): affected from 9.4.0; fixed in 9.4.13 - github.com/grafana/grafana (Go): affected from 9.4.0; fixed in 9.4.13 - grafana (Bitnami): affected from 6.7.0; fixed in 8.5.27, 9.2.20, 9.3.16, 9.4.13, 9.5.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-2023-3128/ (Markdown: https://insights.sbomify.com/CVE-2023-3128/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-3128 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-3128 - OSV: https://osv.dev/vulnerability/CVE-2023-3128 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-3128/ Summaries are generated and may contain mistakes; the official description above is the record.