LiveActive security incident?Get immediate response
CVE Record

CVE-2022-39328: Grafana vulnerable to race condition allowing privilege escalation

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

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Grafana 9.2.0 through 9.2.3 has a race condition that may let an unauthenticated user query an administration endpoint under heavy load. This is critical because administrative access paths can affect monitoring data, configuration, and service integrity. Grafana patched it in 9.2.4, and the source states there are no known workarounds.

Executive priority

Treat as urgent for any affected Grafana deployment, especially external or business-critical monitoring. The fix is version-based and documented, while no workaround is named in the sources.

Technical view

CVE-2022-39328 is a CWE-362 race condition in Grafana authentication middleware logic. The issue is network exploitable with no privileges or user interaction according to CVSS 3.1 score 9.8. Affected versions are Grafana >=9.2.0 and <9.2.4. The documented fix is Grafana 9.2.4.

Likely exposure

Exposure is limited to organizations running Grafana 9.2.0, 9.2.1, 9.2.2, or 9.2.3. Internet-facing Grafana deployments, shared monitoring platforms, and systems under heavy load deserve fastest review.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The condition requires heavy load, but the CVSS vector rates attack complexity low and requires no authentication.

Researcher notes

Focus validation on version detection and exposure mapping. The public description identifies an authentication middleware race condition under heavy load, but the bundle does not provide deeper root-cause details, exploit telemetry, or safe detection indicators beyond affected versions and endpoint context.

Mitigation direction

  • Upgrade affected Grafana instances to 9.2.4 or later.
  • Prioritize internet-facing and shared Grafana deployments.
  • Do not rely on a workaround; sources state none are known.
  • Check Grafana advisory for current vendor guidance.
  • Track any dependent vendor advisories, including NetApp where relevant.

Validation and detection

  • Inventory Grafana versions across production and non-production systems.
  • Flag Grafana 9.2.0 through 9.2.3 as affected.
  • Confirm remediated instances report Grafana 9.2.4 or later.
  • Review whether Grafana admin endpoints are reachable from untrusted networks.
  • Check monitoring for unusual unauthenticated admin endpoint requests.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-362: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-39328 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-39328Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
grafanagrafana>= 9.2.0, < 9.2.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-362 · source CWE mapping

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.