Vulnerability record · CVE-2022-31107 · published 15 July 2022
CVE-2022-31107: Grafana incorrect authorization vulnerability
Grafana · Grafana
Grafana is an open-source platform for monitoring and observability. In versions 5.3 until 9.0.3, 8.5.9, 8.4.10, and 8.3.10, it is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP which provides a login name to take over the account of another user in that Grafana instance. This can occur when the malicious user is authorized to log in to Grafana via OAuth, the malicious user's external user id is not already associated with an account in Grafana, the malicious user's email address is not already associated with an account in Grafana, and the malicious user knows the Grafana username of the target user. If these conditions are met, the malicious user can set their username in the OAuth provider to that of the target user, then go through the OAuth flow to log in to Grafana. Due to the way that external and internal user accounts are linked together during login, if the conditions above are all met then the malicious user will be able to log in to the target user's Grafana account. Versions 9.0.3, 8.5.9, 8.4.10, and 8.3.10 contain a patch for this issue. As a workaround, concerned users can disable OAuth login to their Grafana instance, or ensure that all users authorized to log in via OAuth have a corresponding user account in Grafana linked to their email address.
Description
Grafana is an open-source platform for monitoring and observability. In versions 5.3 until 9.0.3, 8.5.9, 8.4.10, and 8.3.10, it is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP which provides a login name to take over the account of another user in that Grafana instance. This can occur when the malicious user is authorized to log in to Grafana via OAuth, the malicious user's external user id is not already associated with an account in Grafana, the malicious user's email address is not already associated with an account in Grafana, and the malicious user knows the Grafana username of the target user. If these conditions are met, the malicious user can set their username in the OAuth provider to that of the target user, then go through the OAuth flow to log in to Grafana. Due to the way that external and internal user accounts are linked together during login, if the conditions above are all met then the malicious user will be able to log in to the target user's Grafana account. Versions 9.0.3, 8.5.9, 8.4.10, and 8.3.10 contain a patch for this issue. As a workaround, concerned users can disable OAuth login to their Grafana instance, or ensure that all users authorized to log in via OAuth have a corresponding user account in Grafana linked to their email address.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected products
2 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://github.com/grafana/grafana/security/advisories/GHSA-mx47-6497-3fv2 | Release NotesThird Party Advisory |
| https://grafana.com/docs/grafana/next/release-notes/release-notes-8-4-10/ | Release NotesVendor Advisory |
| https://grafana.com/docs/grafana/next/release-notes/release-notes-8-5-9/ | Release NotesVendor Advisory |
| https://grafana.com/docs/grafana/next/release-notes/release-notes-9-0-3/ | Release NotesVendor Advisory |
| https://security.netapp.com/advisory/ntap-20220901-0010/ | Third Party Advisory |
| https://github.com/grafana/grafana/security/advisories/GHSA-mx47-6497-3fv2 | Release NotesThird Party Advisory |
| https://grafana.com/docs/grafana/next/release-notes/release-notes-8-4-10/ | Release NotesVendor Advisory |
| https://grafana.com/docs/grafana/next/release-notes/release-notes-8-5-9/ | Release NotesVendor Advisory |
| https://grafana.com/docs/grafana/next/release-notes/release-notes-9-0-3/ | Release NotesVendor Advisory |
| https://security.netapp.com/advisory/ntap-20220901-0010/ | Third Party Advisory |
Track CVE-2022-31107 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2022-31107), CISA KEV, FIRST EPSS (scores of 2026-10-03). This page is refreshed as NVD updates the record.
