Security readout for executives and security teams
Plain-English summary
Grafana Enterprise could temporarily treat a lower-privileged API key as if it had the permissions of a prior higher-privileged key. This only applies when the fine-grained access control beta feature is enabled and multiple API keys with different roles exist in one organization.
Executive priority
Treat this as a high-priority fix for affected Grafana Enterprise environments, especially monitoring systems tied to operational or security workflows. The exposure conditions are specific, so prioritize inventory first, then upgrade or disable FGAC quickly where affected.
Technical view
The flaw is a privilege escalation in Grafana Enterprise FGAC API key permission caching. For about 30 seconds, permissions were cached per organization using an insufficient cache ID, so later API key requests could inherit permissions from an earlier key. Affected versions are from 8.1.0-beta1 before 8.4.6.
Likely exposure
Exposure is narrow: Grafana Enterprise only, FGAC beta enabled, and more than one API key in the same organization with different assigned roles. Open-source Grafana and Enterprise deployments without FGAC enabled are not described as affected in the provided sources.
Exploitation context
The CVSS vector requires high privileges and high attack complexity, but impact is high across confidentiality, integrity, and availability. The source bundle does not show CISA KEV listing or cited active exploitation evidence.
Researcher notes
Key conditions are Enterprise edition, FGAC beta enabled, multiple API keys in one organization, and different roles. Avoid assuming broader Grafana exposure. The core issue is authorization cache confusion, mapped to CWE-269, with CVSS 3.1 score 8.0.
Mitigation direction
- Upgrade affected Grafana Enterprise installations to 8.4.6 or later.
- Disable fine-grained access control if immediate upgrade is not possible.
- Review Grafana vendor guidance for any environment-specific remediation notes.
- Prioritize organizations using multiple API keys with different roles.
Validation and detection
- Identify Grafana Enterprise versions from 8.1.0-beta1 through before 8.4.6.
- Confirm whether fine-grained access control beta is enabled.
- Check whether each organization has multiple API keys with different roles.
- Verify remediation by confirming version 8.4.6 or later, or FGAC disabled.
- Review privileged API activity during periods before remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupPrivilege 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 lookupCVE-2022-24812 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H1.36Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8HighVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/grafana/grafana/security/advisories/GHSA-82gq-xfg3-5j7vCVE reference · x_refsource_CONFIRM
- https://grafana.com/blog/2022/04/12/grafana-enterprise-8.4.6-released-with-high-severity-security-fix/CVE reference · x_refsource_MISC
- https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-4-6/CVE reference · x_refsource_MISC
- https://security.netapp.com/advisory/ntap-20220519-0005/CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.