CVE-2023-2183 — grafana
MEDIUMCVE-2023-2183 is a medium-severity (CVSS 4.1) CWE-284 vulnerability in github.com/grafana/grafana. 1 public exploit reference exists, so weaponization risk is real. A fix is available for github.com/grafana/grafana — see the affected versions and patch details below.
Grafana has Broken Access Control in Alert manager: Viewer can send test alerts
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-2183.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-2183 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafanaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Grafana is an open-source platform for monitoring and observability.
The option to send a test alert is not available from the user panel UI for users having the Viewer role. It is still possible for a user with the Viewer role to send a test alert using the API as the API does not check access to this function.
This might enable malicious users to abuse the functionality by sending multiple alert messages to e-mail and Slack, spamming users, prepare Phishing attack or block SMTP server.
Users may upgrade to version 9.5.3, 9.4.12, 9.3.15, 9.2.19 and 8.5.26 to receive a fix.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/grafana/grafana | all versions | 8.5.26go get github.com/grafana/grafana@v8.5.26 |
| 🐹Go | github.com/grafana/grafana | ≥ 9.0.0&&< 9.2.19 | 9.2.19go get github.com/grafana/grafana@v9.2.19 |
| 🐹Go | github.com/grafana/grafana | ≥ 9.3.0&&< 9.3.15 | 9.3.15go get github.com/grafana/grafana@v9.3.15 |
| 🐹Go | github.com/grafana/grafana | ≥ 9.4.0&&< 9.4.12 | 9.4.12go get github.com/grafana/grafana@v9.4.12 |
| 🐹Go | github.com/grafana/grafana | ≥ 9.5.0&&< 9.5.3 | 9.5.3go get github.com/grafana/grafana@v9.5.3 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/grafana/grafana to 8.5.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-2183 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-2183 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-2183. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
OpenShift ServiceMesh (OSSM) has switched to using upstream rhel rpms for grafana, and is no longer maintaining the servicemesh-grafana package. Hence, it is marked as affected/won'tfix.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Ceph Storage 6.1 | ceph-2:17.2.6-167.el9cp | RHSA-2023:7740 |
| Red Hat Ceph Storage 6.1 | rhceph/rhceph-6-dashboard-rhel9:6-82 | RHSA-2023:7741 |
Frequently Asked Questions
Is CVE-2023-2183 in your dependencies?
O3 Security finds CVE-2023-2183 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.