Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
CRITICAL severity

GHSA-rgjg-66cx-5x9m

CRITICALFix: grafana/grafana@7baecf0

GHSA-rgjg-66cx-5x9m is a critical-severity (CVSS 9.8) Improper Authentication vulnerability in github.com/grafana/grafana. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-rgjg-66cx-5x9m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Grafana Authentication Bypass

Also known asCVE-2018-15727GO-2022-0707
Published
Feb 15, 2022
Updated
Aug 21, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
3 known
Exploitation data as of Aug 21, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
🐹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 before 4.6.4 and 5.x before 5.2.3 allows authentication bypass because an attacker can generate a valid "remember me" cookie knowing only a username of an LDAP or OAuth user.

Specific Go Packages Affected

github.com/grafana/grafana/pkg/api

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/grafana/grafanaall versions4.6.4
🐹Gogithub.com/grafana/grafana5.0.0&&< 5.2.35.2.3
Exploits & PoCs
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 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 4.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rgjg-66cx-5x9m 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 GHSA-rgjg-66cx-5x9m 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 GHSA-rgjg-66cx-5x9m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Grafana before 4.6.4 and 5.x before 5.2.3 allows authentication bypass because an attacker can generate a valid "remember me" cookie knowing only a username of an LDAP or OAuth user. ### Specific Go Packages Affected github.com/grafana/grafana/pkg/api
O3 Security · Impact-Aware SCA

Is GHSA-rgjg-66cx-5x9m in your dependencies?

O3 detects GHSA-rgjg-66cx-5x9m across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-rgjg-66cx-5x9m: Grafana… | O3 Security