dbcve.org
Google SheetsApplication · Grafana

CVE-2023-4457

HIGH · 7.5 CVSS v3.1 Published 2023-10-16
Fix available
A fix is available. Upgrade to after 1.2.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Grafana is an open-source platform for monitoring and observability. The Google Sheets data source plugin for Grafana, versions 0.9.0 to 1.2.2 are vulnerable to an information disclosure vulnerability. The plugin did not properly sanitize error messages, making it potentially expose the Google Sheet API-key that is configured for the data source. This vulnerability was fixed in version 1.2.2.

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

The Google Sheets data source plugin for Grafana (versions 0.9.0 to 1.2.2) improperly sanitizes error messages, which can cause configured Google Sheets API keys to be exposed in error output. This is an information disclosure vulnerability with CVSS 7.5 (HIGH).

MitigationUpdate the Grafana Google Sheets data source plugin to version 1.2.2 or later to remediate the vulnerability.

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
Google SheetsApplication
Affected:>= 0.9.0, <= 1.2.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 if Google Sheets plugin is installed
    Use Grafana CLI command 'grafana-cli plugins ls' or query the Grafana API endpoint /api/plugins to list installed plugins. Look for 'grafana-googlesheets-datasource' or similar Google Sheets data source plugin.
    Affected if The plugin appears in the list of installed plugins
  2. Verify the installed plugin version
    Check the plugin version from the plugin listing output or via the Grafana API at /api/plugins/<plugin-id>. Compare the version to the affected range: 0.9.0 through 1.2.2.
    Affected if The installed version is >= 0.9.0 and <= 1.2.2
  3. Identify configured Google Sheets data sources
    Query the Grafana API at /api/datasources or inspect the Grafana provisioning files to find data sources of type 'googlesheets' or similar. Each configured instance represents a potential exposure point.
    Affected if At least one Google Sheets data source is configured with an API key
  4. Review error logs for API key exposure
    Examine Grafana logs (typically in /var/log/grafana or via the /api/logs endpoint) for error messages related to Google Sheets API calls. Search for patterns where API keys might appear in plaintext within error output.
    Affected if Error logs contain what appear to be Google Sheets API keys in the message content

You are affected if the Google Sheets plugin versions 0.9.0-1.2.2 are installed AND at least one Google Sheets data source with an API key is configured in your Grafana instance.

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 a release after 1.2.2
Interim mitigation

Update the Grafana Google Sheets data source plugin to version 1.2.2 or later to remediate the vulnerability.

Recommended fix High confidence

Google Sheets plugin version 1.2.3 or later

  1. 1. Identify all Grafana instances using the Google Sheets data source plugin.
  2. 2. Check the current installed version of the Google Sheets plugin (typically found in Grafana's plugin catalog or configuration).
  3. 3. Upgrade the Google Sheets plugin to version 1.2.3 or later.
  4. 4. Verify the upgrade was successful by checking the plugin version in Grafana.
  5. 5. Test that the Google Sheets data source functions correctly with the updated plugin.
  6. 6. Confirm that error messages no longer expose sensitive information (API keys) by triggering a test connection.

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

Fix this in Google Sheets Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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