| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/grafana/grafana | ≥ 2.0.0-beta1, < 7.5.15≥ 8.0.0, < 8.3.5 | 7.5.158.3.5 |
| grafana | = 2.0.0≥ 2.0.1, < 7.5.15≥ 8.0.0, < 8.3.5 | 7.5.158.3.5 |
| e-series performance analyzer | < 3.0 | 3.0 |
Today we are releasing Grafana 8.3.5 and 7.5.15. This patch release includes MEDIUM severity security fix for XSS for Grafana.
Release v.8.3.5, only containing security fixes:
Release v.7.5.15, only containing security fixes:
On Jan. 16, an external security researcher, Jasu Viding contacted Grafana to disclose an XSS vulnerability in the way that Grafana handles data sources.
An attacker could serve HTML content through the Grafana datasource or plugin proxy and trick a user to visit this HTML page using a specially crafted link and execute a Cross-site Scripting (XSS) attack. The attacker could either compromise an existing datasource for a specific Grafana instance or either set up its own public service and instruct anyone to set it up in their Grafana instance.
We believe that this vulnerability is rated at CVSS 6.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N).
Should an existing data source connected to Grafana be compromised, it could be used to inappropriately gain access to other data sources connected to the same Grafana org.
To be impacted, all of the following must be applicable:
For data source proxy:
For plugin proxy:
Backend plugin resource:
Reproduced and confirmed via this Golang app:
package main
import (
"fmt"
"log"
"net/http"
)
func main() {
http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
fmt.Fprintf(w, "<html><body><script>alert('XSS');</script></body></html>")
})
log.Fatal(http.ListenAndServe(":3011", nil))
}
A Prometheus datasource is configured in Grafana with URL http://localhost:3011.
When visitining http://localhost:3000/api/datasources/proxy/170 the scripts declared in the HTML page executes. Confirmed in both Chrome and Firefox.
All installations between Grafana v2.0.0-beta1 up to v8.3.4 should be upgraded as soon as possible.
Using a proxy, set a response header Content Security Policy: sandbox for the following routes:
/api/datasources/proxy*
/api/plugin-proxy*
/api/plugins/<pluginId>/resources*
/api/datasources/<id>/resources*
Another possible mitigation is setting the response header Content-Disposition: attachment; “proxy.txt”. Confirmed in both Chrome and Firefox.
Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC.
We would like to thank Jasu Viding for responsibly disclosing the vulnerability.
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.
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free