CVE-2022-31107

Today we are releasing Grafana 8.3.10, 8.4.10, 8.5.9 and 9.0.3. This patch release includes a HIGH severity security fix for an Oauth takeover vulnerability in Grafana.

Release v.9.0.3, containing this security fix and other patches:

• Download Grafana 9.0.3
• Release notes

Release v.8.5.9, containing this security fix and other fixes:

• Download Grafana 8.5.9
• Release notes

Release v.8.4.10, containing this security fix and other fixes:

• Download Grafana 8.4.10
• Release notes

Release v.8.3.10, containing this security fix and other fixes:

• Download Grafana 8.3.10

Grafana account takeover via OAuth vulnerability (CVE-2022-31107)

On June 27 the HTTPVoid team contacted Grafana Labs to disclose a Grafana account takeover via an OAuth vulnerability.

We believe that this vulnerability is rated at CVSS 7.1 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L).

Affected versions with HIGH severity

All Grafana >=5.3 versions are affected by this vulnerability.

Solutions and mitigations

All installations after Grafana v5.3 should be upgraded as soon as possible.

As a workaround it is possible to disable any OAuth login or ensure that all users authorized to log in via OAuth have a corresponding user account in Grafana linked to their email address.

Appropriate patches have been applied to Grafana Cloud and as always, we closely coordinated with all cloud providers licensed to offer Grafana Pro. They have received early notification under embargo and confirmed that their offerings are secure at the time of this announcement. This is applicable to Amazon Managed Grafana.

Timeline

Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC.

2022-06-27 19:00 - Research submission of vulnerability report
2022-06-27 20:53 - Issue triaged, confirmed positive, and internal incident raised
2022-06-28 08:42 - Fix PR submitted and reviewed
2022-06-28 20:58 - All Grafana Cloud hosted Grafana instances patched
2022-07-05 07:14 - Customers informed under embargo
2022-07-14 02:00 - Public release

Acknowledgement

We would like to thank the HTTPVoid team for responsibly disclosing the vulnerability.

Reporting security issues

If you think you have found a security vulnerability, please send a report to [email protected]. This address can be used for all of Grafana Labs' open source and commercial products (including, but not limited to Grafana, Grafana Cloud, Grafana Enterprise, and grafana.com). We can accept only vulnerability reports at this address. We would prefer that you encrypt your message to us by using our PGP key. The key fingerprint is

F988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA

The key is available from keyserver.ubuntu.com.

Security announcements

We maintain a security category on our blog, where we will always post a summary, remediation, and mitigation details for any patch containing security fixes.

You can also subscribe to our RSS feed.

It is possible for a malicious user who has authorization to log into a Grafana instance via a configured OAuth IdP to take over an existing Grafana account under some conditions.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2022-31107 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.4.10, 8.5.9, 9.0.3, 8.3.10); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-31107? CVE-2022-31107 is a high-severity incorrect authorization vulnerability in github.com/grafana/grafana (go), affecting versions >= 8.4.0, < 8.4.10. It is fixed in 8.4.10, 8.5.9, 9.0.3, 8.3.10. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2022-31107? CVE-2022-31107 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/grafana/grafana are affected by CVE-2022-31107? github.com/grafana/grafana (go) versions >= 8.4.0, < 8.4.10 is affected.
4. Is there a fix for CVE-2022-31107? Yes. CVE-2022-31107 is fixed in 8.4.10, 8.5.9, 9.0.3, 8.3.10. Upgrade to this version or later.
5. Is CVE-2022-31107 exploitable, and should I be worried? Whether CVE-2022-31107 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-31107 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-31107?
   • Upgrade github.com/grafana/grafana to 8.4.10 or later
   • Upgrade github.com/grafana/grafana to 8.5.9 or later
   • Upgrade github.com/grafana/grafana to 9.0.3 or later
   • Upgrade github.com/grafana/grafana to 8.3.10 or later