dbcve.org
GrafanaApplication

CVE-2024-9264

HIGH · 8.8 CVSS v3.1 Published 2024-10-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
High EPSS Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Grafana's experimental SQL Expressions feature allows execution of duckdb queries with user input. Insufficient input sanitization enables command injection and local file inclusion attacks. Exploitation requires only VIEWER-level authentication and depends on duckdb being present in the system PATH, which is not the default Grafana configuration.

MitigationDisable the SQL Expressions experimental feature if enabled, ensure duckdb is not installed or not in Grafana's $PATH, and apply vendor patches when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GrafanaApplication
Affected:= 11.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Grafana version
    Run 'grafana-server -v' or check the Grafana admin UI at /api/health to find the installed version number
    Affected if The installed version is exactly 11.0.0 (other versions are not affected by this specific CVE)
  2. Verify SQL Expressions feature is enabled
    Inspect Grafana configuration file (grafana.ini) or environment variables for 'feature_toggles' containing 'sqlExpressions' or 'enable: true' under the [feature_toggles] section
    Affected if The SQL Expressions experimental feature is enabled in the configuration
  3. Confirm duckdb is in Grafana's PATH
    Run 'which duckdb' or 'where duckdb' from the same environment/user that runs Grafana, or check if duckdb binary exists in system PATH
    Affected if The duckdb executable is accessible in the system PATH accessible to Grafana (this is required for exploitation but not default)
  4. Verify authentication is enabled
    Check that Grafana's authentication is properly configured and not left in anonymous mode, or review user role assignments
    Affected if Viewer-level or higher users can access Grafana (exploitation requires only Viewer authentication)
  5. Inspect SQL Expressions configuration
    Check Grafana's configuration for any custom SQL expression data sources or experimental feature flags in the settings
    Affected if SQL Expressions feature appears to be actively configured or used in the environment

You are affected if you are running Grafana version 11.0.0 with the SQL Expressions experimental feature enabled and duckdb is present in the system PATH accessible to Grafana.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the SQL Expressions experimental feature if enabled, ensure duckdb is not installed or not in Grafana's $PATH, and apply vendor patches when available.

Recommended fix High confidence

Grafana 11.0.1 or later (check grafana.com for the latest stable 11.x release)

  1. 1. Identify your current Grafana version by checking the grafana-server version or the UI at Administration > Stats & licensing
  2. 2. Back up your Grafana configuration files (grafana.ini, provisioning directories, and any custom dashboards)
  3. 3. If using a package manager (apt, yum, docker), upgrade Grafana to version 11.0.1 or later
  4. 4. For manual installations, download the updated binary/package from grafana.com/grafana/download
  5. 5. Restart the Grafana service after upgrading
  6. 6. Verify the upgrade was successful by checking the version in the UI or via API
  7. 7. If you do not need the SQL Expressions feature, consider disabling experimental features in your grafana.ini by setting enable_experimental_features = false
Caveat Minimal risk - this fixes a security vulnerability in an experimental feature; ensure any custom SQL Expressions dashboards are re-tested after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grafana Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9264 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9264 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data