Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

Google Cloud Platform (GCP) Cross-Tenant SQL Injection on Big Query and Spanner Through the Linking API in Looker Studio

High

Synopsis

Tenable Research has identified and responsibly disclosed a critical SQL injection vulnerability in Looker Studio's Linking API. This flaw allowed attackers to craft a malicious URL that could execute arbitrary SQL queries on a victim's BigQuery data source.

 

The vulnerability exploited the CUSTOM_QUERY and BIG_QUERY connector types within the Linking API. An attacker could construct a specific URL containing a malicious SQL payload in the ds.*.sql parameter. When a victim clicked this link, Looker Studio would automatically create a temporary report, connect to the victim's BigQuery account, and execute the attacker's SQL query. This could lead to a one-click exfiltration of all datasets and tables the victim had access to. The vulnerability could also be used to insert, delete, or modify data, depending on the victim's permissions.

 

Proof of Concept

  1. Craft the Linking API link with the victim’s project ID and the SQL injection you wish to run
  2. Visit the Linking API link that the attacker has crafted as the victim

https://lookerstudio.google.com/u/0/reporting/create?ds.type=CUSTOM_QUERY&ds.connector=BIG_QUERY&ds.billingProjectId=<PROJECT>&ds.projectId=<PROJECT>&ds.*.sql=<MALICIOUS QUERY>

  1. Malicious SQL will run in your Big Query, in the context of your user.

Disclosure Timeline

June 3, 2025 - Tenable reported the finding to Google, and Google acknowledges
June 9, 2025 - Google assigns S1 severity
June 26, 2025 - Google awards a bounty
July 2, 2025 - Tenable asks for updates on the fix
July 15, 2025 - Tenable asks for updates
July 17, 2025 - Google updates that the product team is working to resolve the issue
July 28, 2025 - Google provides an update regarding the fix
July 31, 2025 - Tenable agrees to delay the disclosure date while Google is actively working
August 26, 2025 - Google updates that the mitigation is expected around mid-September
September 12, 2025 - Google requests the TRA to be published on 10/01/2025
September 15, 2025 - Tenable agrees to Google's request

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]

Risk Information

Tenable Advisory ID: TRA-2025-37
Credit:
Liv Matan
Affected Products:
GCP Looker Studio
Risk Factor:
High

Advisory Timeline

October 1, 2025 - Initial Release.
× Contact our sales team