GrafanaApplication
CVE-2022-39328
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGrafana is an open-source platform for monitoring and observability. Versions starting with 9.2.0 and less than 9.2.4 contain a race condition in the authentication middlewares logic which may allow an unauthenticated user to query an administration endpoint under heavy load. This issue is patched in 9.2.4. There are no known workarounds.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA race condition exists in Grafana's authentication middleware between versions 9.2.0 and 9.2.3. Under heavy load conditions, this timing vulnerability can allow an unauthenticated attacker to bypass authentication and query administrative endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GrafanaApplication
>= 9.2.0, < 9.2.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Grafana versionRun 'grafana-server -v' or check the version file typically at /usr/share/grafana/version, or query the Grafana API at /api/healthAffected if Version is 9.2.0, 9.2.1, 9.2.2, or 9.2.3 (anything >= 9.2.0 and < 9.2.4)
-
Confirm instance is network accessibleCheck Grafana bind address configuration in grafana.ini (http_addr) and verify firewall or networkACLs allow external access to the Grafana port (default 3000)Affected if Grafana is reachable from untrusted networks on port 3000 or configured HTTP port
You are affected if your Grafana version is 9.2.0 through 9.2.3 AND the instance is network-accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.2.4
Upgrade Grafana to version 9.2.4 or later to patch the race condition vulnerability. No workarounds are available.
9.2.4 or later (9.3.x stable recommended for additional fixes)
- 1. Identify your current Grafana installation method (package manager, Docker, binary, etc.)
- 2. Backup your Grafana configuration files and data directory
- 3. For package manager installations: run the appropriate update command (e.g., apt-get update && apt-get install grafana for Debian/Ubuntu, or yum update grafana for RHEL/CentOS)
- 4. For Docker: pull the new image (docker pull grafana/grafana:9.2.4) and recreate your container with the same configuration
- 5. Verify the upgrade by checking Grafana version at /api/health or the admin UI
- 6. Test that authentication and admin endpoints are functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Grafana
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-39328 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data