MediumGHSA-63g3-9jq3-mccvBIT-grafana-2022-21713CVE-2022-21713

Grafana API IDOR

Published 14 May 2024 · Updated 14 May 2024

Is your project on an affected github.com/grafana/grafana?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=5.0.0-beta1 <7.5.15
Fixed in
7.5.15
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v7.5.15
Affected
>=8.0.0 <8.3.5
Fixed in
8.3.5
Update to the fixed version for your release line, for example:go get github.com/grafana/grafana@v8.3.5

Details

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:

Release v.7.5.15, only containing security fixes:

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).

Impact

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.

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 security@grafana.com. 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.

Is GHSA-63g3-9jq3-mccv in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/grafana/grafana, and gives you the command that fixes it.

More advisories for github.com/grafana/grafana

  • LowCVE-2026-21727Grafana legacy correlations allow cross-tenant disclosure and deletion in github.com/grafana/grafana · 7 Oct 2026
  • LowCVE-2026-42127Grafana: Pre-authentication denial of service in the public dashboard query handler in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-9029Grafana geomap panel's XYZ tile layer has a sanitize-then-interpolate ordering bug in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-42129Grafana Loki datasource plugin's callResource handler contains a path traversal vulnerability. in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-10601Grafana: Path traversal in the Tempo and Loki data source plugins in github.com/grafana/grafana · 28 Sept 2026
  • LowCVE-2026-33381Grafana: Users can generate Service Account tokens after permissions removal in github.com/grafana/grafana · 25 Jun 2026
All 113 advisories for github.com/grafana/grafana

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.