First published: Tue Apr 12 2022(Updated: )
Grafana is an open-source platform for monitoring and observability. When fine-grained access control is enabled and a client uses Grafana API Key to make requests, the permissions for that API Key are cached for 30 seconds for the given organization. Because of the way the cache ID is constructed, the consequent requests with any API Key evaluate to the same permissions as the previous requests. This can lead to an escalation of privileges, when for example a first request is made with Admin permissions, and the second request with different API Key is made with Viewer permissions, the second request will get the cached permissions from the previous Admin, essentially accessing higher privilege than it should. The vulnerability is only impacting Grafana Enterprise when the fine-grained access control beta feature is enabled and there are more than one API Keys in one organization with different roles assigned. All installations after Grafana Enterprise v8.1.0-beta1 should be upgraded as soon as possible. As an alternative, disable fine-grained access control will mitigate the vulnerability.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Grafana Grafana | >=8.1.0<8.4.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-24812 is a vulnerability in Grafana that allows cached permissions for a Grafana API Key to be accessed by unauthorized clients.
The severity of CVE-2022-24812 is high with a CVSS score of 8.8.
CVE-2022-24812 affects Grafana versions 8.1.0 to 8.4.6 with fine-grained access control enabled and when using Grafana API Key for requests.
Yes, Grafana Enterprise version 8.4.6 includes a security fix for CVE-2022-24812.
You can find more information about CVE-2022-24812 in the Grafana security advisory and release notes.