CVE-2021-43798: Grafana Path Traversal Vulnerability

Grafana is an open-source platform for monitoring and observability. Grafana versions 8.0.0-beta1 through 8.3.0 (except for patched versions) iss vulnerable to directory traversal, allowing access to local files. The vulnerable URL path is: <grafanahosturl>/public/plugins//, where is the plugin ID for any installed plugin. At no time has Grafana Cloud been vulnerable. Users are advised to upgrade to patched versions 8.0.7, 8.1.8, 8.2.7, or 8.3.1. The GitHub Security Advisory contains more information about vulnerable URL paths, mitigation, and the disclosure timeline.

Today we are releasing Grafana 8.3.1, 8.2.7, 8.1.8, 8.0.7. This patch release includes a high severity security fix that affects Grafana versions from v8.0.0-beta1 through v8.3.0.

Release v8.3.1, only containing a security fix:

- Download Grafana 8.3.1 - Release notes

Release v8.2.7, only containing a security fix:

- Download Grafana 8.2.7 - Release notes

Release v8.1.8, only containing a security fix:

- Download Grafana 8.1.8 - Release notes

Release v8.0.7, only containing a security fix:

- Download Grafana 8.0.7 - Release notes

Path Traversal (CVE-2021-43798)

Summary

On 2021-12-03, we received a report that Grafana is vulnerable to directory traversal, allowing access to local files. We have confirmed this for versions 8.0.0-beta1 to 8.3.0. Thanks to our defense-in-depth approach, at no time has Grafana Cloud been vulnerable.

The vulnerable URL path is: <grafanahosturl>/public/plugins/<plugin-id>/, where <plugin-id> is the plugin ID for any installed plugin.

Every Grafana instance comes with pre-installed plugins like the Prometheus plugin or MySQL plugin so the following URLs are vulnerable for every instance:

<grafanahosturl>/public/plugins/alertlist/ <grafanahosturl>/public/plugins/annolist/ <grafanahosturl>/public/plugins/barchart/ <grafanahosturl>/public/plugins/bargauge/ <grafanahosturl>/public/plugins/candlestick/ <grafanahosturl>/public/plugins/cloudwatch/ <grafanahosturl>/public/plugins/dashlist/ <grafanahosturl>/public/plugins/elasticsearch/ <grafanahosturl>/public/plugins/gauge/ <grafanahosturl>/public/plugins/geomap/ <grafanahosturl>/public/plugins/gettingstarted/ <grafanahosturl>/public/plugins/grafana-azure-monitor-datasource/ <grafanahosturl>/public/plugins/graph/ <grafanahosturl>/public/plugins/heatmap/ <grafanahosturl>/public/plugins/histogram/ <grafanahosturl>/public/plugins/influxdb/ <grafanahosturl>/public/plugins/jaeger/ <grafanahosturl>/public/plugins/logs/ <grafanahosturl>/public/plugins/loki/ <grafanahosturl>/public/plugins/mssql/ <grafanahosturl>/public/plugins/mysql/ <grafanahosturl>/public/plugins/news/ <grafanahosturl>/public/plugins/nodeGraph/ <grafanahosturl>/public/plugins/opentsdb <grafanahosturl>/public/plugins/piechart/ <grafanahosturl>/public/plugins/pluginlist/ <grafanahosturl>/public/plugins/postgres/ <grafanahosturl>/public/plugins/prometheus/ <grafanahosturl>/public/plugins/stackdriver/ <grafanahosturl>/public/plugins/stat/ <grafanahosturl>/public/plugins/state-timeline/ <grafanahosturl>/public/plugins/status-history/ <grafanahosturl>/public/plugins/table/ <grafanahosturl>/public/plugins/table-old/ <grafanahosturl>/public/plugins/tempo/ <grafanahosturl>/public/plugins/testdata/ <grafanahosturl>/public/plugins/text/ <grafanahosturl>/public/plugins/timeseries/ <grafanahosturl>/public/plugins/welcome/ <grafanahosturl>/public/plugins/zipkin/

We have received CVE-2021-43798 for this issue. The CVSS score for this vulnerability is 7.5 High (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) for Grafana versions 8.0.0-beta1 to 8.3.0

Affected versions with high severity

Grafana 8.0.0-beta1 to 8.3.0

Solutions and mitigations

All installations between v8.0.0-beta1 and v8.3.0 should be upgraded as soon as possible.

If you can not upgrade, running a reverse proxy in front of Grafana that normalizes the PATH of the request will mitigate the vulnerability. For example the normalizepath setting in envoy.

Thanks to our defense-in-depth approach, Grafana Cloud instances have not been affected by the vulnerability.

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. In alphabetical order, this is applicable to Amazon Managed Grafana, and Azure Managed Grafana.

Timeline and postmortem

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

2021-12-03: Security researcher sends the initial report 2021-12-03: Confirmed for 8.0.0-beta1 through 8.3.0 2021-12-03: Confirmed that Grafana Cloud is not vulnerable 2021-12-03: Security fix determined and committed to Git 2021-12-03: Release timeline determined: 2021-12-07 for private customer release, 2021-12-14 for public release 2021-12-06: Second report about the vulnerability received 2021-12-07: We received information that the vulnerability has been leaked to the public, turning it into a 0 day 2021-12-07: Decision made to release as quickly as feasible 2021-12-07: Private release with reduced two hour grace period instead of the usual 1 week 2021-12-07: Public release

Acknowledgements

We would like to thank Jordy Versmissen for finding the vulnerability and alerting us to it.

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.

— GitHub