CVE-2022-21713 is a medium-severity (CVSS 4.3) CWE-863 vulnerability in github.com/grafana/grafana. A fix is available for github.com/grafana/grafana — see the affected versions and patch details below.
Exposure of Sensitive Information in Grafana
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-21713.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-21713 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/grafana/grafana🐹github.com/grafana/grafanaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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 [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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/grafana/grafana | ≥ 5.0.0-beta1&&< 7.5.15 | 7.5.15go get github.com/grafana/grafana@v7.5.15 |
| 🐹Go | github.com/grafana/grafana | ≥ 8.0.0&&< 8.3.5 | 8.3.5go get github.com/grafana/grafana@v8.3.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/grafana/grafana to 7.5.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-21713 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-21713 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-21713. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 8 | grafana-0:7.5.15-3.el8 | RHSA-2022:7519 |
| Red Hat Enterprise Linux 9 | grafana-0:7.5.15-3.el9 | RHSA-2022:8057 |
Frequently Asked Questions
Is CVE-2022-21713 in your dependencies?
O3 Security finds CVE-2022-21713 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.