CVE-2022-39328 json
Grafana vulnerable to race condition allowing privilege escalation
published 2022-11-08 4 y ago modified 2026-09-10 59 d ago also BIT-grafana-2022-39328 , EUVD-2024-1814 , GHSA-vqc4-mpj8-jxch , GO-2024-2856
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/grafana/grafana 9.2.4
- bitnami grafana 9.2.4
- grafana grafana 9.2.4
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-39328 updated cvss 8.1
grafana: race condition allowing privilege escalation
-
Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/logging-loki-rhel8, openshift-logging/logging-view-plugin-rhel9 Red Hat OpenShift Service Mesh 2 openshift-service-mesh/grafana-rhel8 Red Hat OpenShift Service Mesh 2.0 servicemesh-grafana, servicemesh-grafana-prometheus, openshift-service-mesh/grafana-rhel8 Red Hat OpenShift Service Mesh 2.1 servicemesh-grafana, openshift-service-mesh/grafana-rhel8 Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/acm-grafana-rhel8 Red Hat build of Quarkus grafananot affected: vulnerable code not present
+9 more productsfewer
Red Hat Ceph Storage 3 grafana Red Hat Ceph Storage 4 rhceph/rhceph-4-dashboard-rhel8 Red Hat Ceph Storage 5 rhceph/rhceph-5-dashboard-rhel8 Red Hat Enterprise Linux 8 grafana, grafana-loki, grafana-mssql, grafana-mysql, grafana-selinux, grafana-graphite, +8 more Red Hat Enterprise Linux 9 grafana, grafana-selinux Red Hat OpenShift Container Platform 3.11 openshift3/grafana Red Hat OpenShift Container Platform 4 openshift4/ose-grafana, openshift4/ose-prometheus, openshift4/ose-thanos-rhel8, openshift4/ose-prometheus-rhel9-operator, openshift4/ose-cluster-monitoring-rhel9-operator Red Hat OpenShift GitOps openshift-gitops-1/gitops-rhel8-operator Red Hat Storage 3 grafana
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 9 mo ago
Exploit prediction
1.30% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/grafana/grafana | >=9.2.0, <9.2.4 all versions |
9.2.4 |
| bitnami | grafana | >=9.2.0, <9.2.4 |
9.2.4 |
Affected products
- grafana grafana
Classification
- Weakness
-
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
References
-
github.com
/grafana/grafana/security/advisories/GHSA-vqc4-mpj8-jxch
web, vendor-advisory, advisory
-
security.netapp.com
/advisory/ntap-20221215-0003/
third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-39328
advisory, web
-
github.com
/grafana/grafana
package
-
security.netapp.com
/advisory/ntap-20221215-0003
web
Sources
- CVE List CVE-2022-39328
- GitHub Advisory GHSA-vqc4-mpj8-jxch
- NVD CVE-2022-39328
- OSV BIT-grafana-2022-39328
- OSV GO-2024-2856
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.