Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2023-2183

MEDIUM

CVE-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. O3 Security confirms whether CVE-2023-2183 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Grafana has Broken Access Control in Alert manager: Viewer can send test alerts

Also known asBIT-grafana-2023-2183GHSA-cvm3-pp2j-chr3
Published
Jun 6, 2023
Updated
Jul 15, 2026
Affected
5 pkgs
Patched
5 / 5
Exploits
1 known

Blast Radius

5 pkgs affected
🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana

Real-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

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/grafana/grafanaall versions8.5.26
🐹Gogithub.com/grafana/grafana9.0.0&&< 9.2.199.2.19
🐹Gogithub.com/grafana/grafana9.3.0&&< 9.3.159.3.15
🐹Gogithub.com/grafana/grafana9.4.0&&< 9.4.129.4.12
🐹Gogithub.com/grafana/grafana9.5.0&&< 9.5.39.5.3
Exploits & PoCs
1

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 dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-2183 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2023-2183 in your dependencies?

O3 detects CVE-2023-2183 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.