Grafana SQL Expressions allow for remote code execution
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in +security-01, 11.0.6+security-01, 11.1.7+security-01, 11.2.2+security-01
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 Metasploit module, 14 proofs of concept on GitHub, 1 Nuclei template
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
The SQL Expressions experimental feature of Grafana allows for the evaluation of `duckdb` queries containing user input. These queries are insufficiently sanitized before being passed to `duckdb`, leading to a command injection and local file inclusion vulnerability. Any user with the VIEWER or higher permission is capable of executing this attack. The `duckdb` binary must be present in Grafana's $PATH for this attack to function; by default, this binary is not installed in Grafana distributions.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Grafana Grafana
From 11.0.0 · fixed in +security-01; From 11.1.0 · fixed in +security-01; From 11.2.0 · fixed in +security-01; From 11.0.0 · fixed in +security-01; From 11.1.0 · fixed in +security-01; From 11.2.0 · fixed in +security-01
- github.com/grafana/grafanaGo
All versions
- github.com/grafana/grafanaGo
From 11.0.0 · fixed in 11.0.6+security-01
- github.com/grafana/grafanaGo
From 11.1.0 · fixed in 11.1.7+security-01
- github.com/grafana/grafanaGo
From 11.2.0 · fixed in 11.2.2+security-01