CVE-2022-21713

Today we are releasing Grafana 8.3.5 and 7.5.14. This patch release includes MEDIUM severity security fix for Grafana Teams API IDOR.

Release v.8.3.5, only containing security fixes:

• Download Grafana 8.3.5
• Release notes

Release v.7.5.15, only containing security fixes:

• Download Grafana 7.5.15
• Release notes

Teams API IDOR(CVE-2022-21713)

On Jan. 18, an external security researcher, Kürşad ALSAN from NSPECT.IO (@nspectio on Twitter), contacted Grafana to disclose an IDOR (Insecure Direct Object Reference) vulnerability on Grafana Teams APIs.

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

Affected versions with MEDIUM severity

All Grafana >=5.0.0-beta1 versions are affected by this vulnerability.

Solutions and mitigations

All installations after Grafana v5.0.0-beta1 should be upgraded as soon as possible.

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 and postmortem

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

• 2022-01-18 05:000 Issue submitted by external researcher
• 2022-01-21 17:45 Issue escalated and the vulnerability confirmed reproducible
• 2022-01-24 13:37 CVE requested
• 2022-01-24 14:40 Private release planned for 2022-01-25, and public release planned for 2022-02-01.
• 2022-01-24 17:00 PR with fix opened
• 2022-01-24 19:00 GitHub has issued CVE-2022-21713
• 2022-01-25 12:00 Private release
• 2022-02-01 12:00 During public release process, we realized that private 7.x release was incomplete. Abort public release, send second private release to customers using 7.x
• 2022-02-08 13:00 Public release

Acknowledgements

We would like to thank Kürşad ALSAN from NSPECT.IO (@nspectio on Twitter) 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.

This vulnerability only impacts the following API endpoints:

• /teams/:teamId - an authenticated attacker can view unintended data by querying for the specific team ID.
• /teams/:search - an authenticated attacker can search for teams and see the total number of available teams, including for those teams that the user does not have access to.
• /teams/:teamId/members - when editors_can_admin flag is enabled, an authenticated attacker can see unintended data by querying for the specific team ID.

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-21713 has a CVSS score of 4.3 (Medium). 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 (7.5.15, 8.3.5); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-21713? CVE-2022-21713 is a medium-severity incorrect authorization vulnerability in github.com/grafana/grafana (go), affecting versions >= 5.0.0-beta1, < 7.5.15. It is fixed in 7.5.15, 8.3.5. 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-21713? CVE-2022-21713 has a CVSS score of 4.3 (Medium). 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-21713? github.com/grafana/grafana (go) versions >= 5.0.0-beta1, < 7.5.15 is affected.
4. Is there a fix for CVE-2022-21713? Yes. CVE-2022-21713 is fixed in 7.5.15, 8.3.5. Upgrade to this version or later.
5. Is CVE-2022-21713 exploitable, and should I be worried? Whether CVE-2022-21713 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-21713 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-21713?
   • Upgrade github.com/grafana/grafana to 7.5.15 or later
   • Upgrade github.com/grafana/grafana to 8.3.5 or later