Vulnerability in github.com/grafana/grafana (CVE-2023-3128)
Summary
Vulnerability in github.com/grafana/grafana (CVE-2023-3128). Confidential information can be exposed externally. Mitigation: upgrade to 8.5.27 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2023-3128 has been found in github.com/grafana/grafana.
Confidential information can be exposed externally.
What to do: upgrade github.com/grafana/grafana to 8.5.27 or later.
If unsure, ask your IT team or search "github.com/grafana/grafana CVE-2023-3128" on the vendor's site.
CVE-2023-3128 (github.com/grafana/grafana) — CWE-290
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.5.27 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-290) exists in github.com/grafana/grafana.
Check the vendor advisory for the affected versions of github.com/grafana/grafana.
Severity: ?. Confidential information can be exposed externally.
Update to 8.5.27.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/grafana/grafana' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/grafana/grafana' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/grafana/grafanaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/grafana/grafana to 8.5.27ステージング環境で 8.5.27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory grafana.com
- advisory security.netapp.com
- package github.com
- web nvd.nist.gov
- web github.com
- web grafana.com
- web security.netapp.com