dbcve.org
GrafanaApplication

CVE-2024-1442

HIGH · 8.8 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to 9.5.7 / 10.0.12 or later.
See remediation →
94/100
Remediation priority · Urgent
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
A user with the permissions to create a data source can use Grafana API to create a data source with UID set to *. Doing this will grant the user access to read, query, edit and delete all data sources within the organization.

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 · moderate confidence

In Grafana, a user with data source creation permissions can use the API to create a data source with UID set to '*' (asterisk). This wildcard UID grants the user implicit elevated permissions to read, query, edit, and delete all data sources within the organization, effectively bypassing access controls.

MitigationUpgrade to the patched Grafana version that rejects wildcard characters in data source UIDs, and audit access logs for any data sources with UID='*' that may indicate exploitation.

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:>= 8.5.0, < 9.5.7>= 10.0.0, < 10.0.12>= 10.1.0, < 10.1.8>= 10.2.0, < 10.2.5>= 10.3.0, < 10.3.4

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 installed Grafana version
    Run `grafana-cli --version` or check Help > About in the Grafana UI, or query the API at GET /api/health
    Affected if The version is >= 8.5.0 and < 9.5.7, or >= 10.0.0 and < 10.0.12, or >= 10.1.0 and < 10.1.8, or >= 10.2.0 and < 10.2.5, or >= 10.3.0 and < 10.3.4
  2. Verify if data source creation permissions exist for non-admin users
    In Grafana, go to Configuration > Users and access management > Teams or Roles, or query the API at GET /api/access-control/users/permissions to see which users have datasources:write permission
    Affected if Any user other than Org Admins has data source creation permissions (datasources:write) and the Grafana version is vulnerable
  3. Inspect existing data sources for wildcard UID
    Query the Grafana API at GET /api/datasources and check the uid field of each returned data source, or inspect the datasource table in the Grafana database
    Affected if Any data source exists where the uid field is set to '*' (asterisk)

A user is affected if they run a vulnerable Grafana version AND have non-admin users with data source creation permissions, or if a data source with UID='*' already exists in the environment.

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
Upgrade available Upgrade to 9.5.7 / 10.0.12 / 10.1.8 or later
Fixed in 9.5.710.0.1210.1.8
Interim mitigation

Upgrade to the patched Grafana version that rejects wildcard characters in data source UIDs, and audit access logs for any data sources with UID='*' that may indicate exploitation.

Recommended fix High confidence

Upgrade to Grafana 9.5.7, 10.0.12, 10.1.8, 10.2.5, or later (preferably latest 10.x release)

  1. 1. Identify your current Grafana version by checking the Grafana UI (Settings > About) or running `grafana-server -v`
  2. 2. Determine which upgrade path applies based on your current version (8.5.x-9.5.x, 10.0.x, 10.1.x, or 10.2.x)
  3. 3. Backup your Grafana configuration, dashboards, and database before upgrading
  4. 4. For installations using Grafana Cloud, use the Cloud portal to update to the latest patched version
  5. 5. For self-managed installations, download the appropriate fixed version (9.5.7, 10.0.12, 10.1.8, 10.2.5, or later) from grafana.com
  6. 6. Follow the standard Grafana upgrade procedure for your deployment method (deb, rpm, docker, or binary)
  7. 7. After upgrade, verify the Grafana server starts successfully and all data sources are accessible
  8. 8. Confirm the vulnerability is remediated by testing that users cannot create data sources with UID set to "*"
Caveat Check Grafana release notes for your target version for any breaking changes or migration requirements

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

Fix this in Grafana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1442 — 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-1442 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