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 Denial of Wallet Through Big Query in Looker Studio

Low

Synopsis

Tenable Research has identified and responsibly disclosed a "Denial of Wallet" vulnerability in Looker Studio. This vulnerability allowed an attacker to abuse the Looker Studio Linking API to exhaust a victim's cloud service billing account without their knowledge.

 

This attack exploited a flaw in the Looker Studio Linking API's handling of billing information. An attacker could craft a malicious URL that, when clicked, would attach a victim's BigQuery billing project ID to an attacker-owned, public report. This report was designed to execute a large number of resource-intensive queries, each of which would run on the victim's billing account.

 

By creating a report with hundreds or even thousands of charts, each triggering a separate BigQuery job, the attacker could launch a denial-of-wallet attack. When the victim visited the malicious link, the queries would execute in their GCP project, consuming their BigQuery quota and running up significant costs on their bill without their consent or knowledge. The attack could be applied to any cloud data source that bills for resource consumption.

 

Proof of Concept

Set up a mock data source:

  1. Create a BigQuery data set and a table. For example, we will name the dataset “attackerdataset” and the table “attackertable” and make them public. Alternatively, you can choose a public BigQuery dataset and table for this step

Set up the attacker’s report:

  1. Create a report.
  2. Choose the Big Query connector.
  3. Choose the specific data source created in the first step: , “attacker’s-project.attackerdataset.attackertable”
  4. Add a chart to the report, preferably a table, by pressing “Add a chart” and choosing a Table. Create hundreds of them, each table is a job that exhausts the billing of the victim when run.
  5. Share the report with the victim, and uncheck the “Notify” checkbox
  6. Craft the Linking API link and input the report ID of the report you just created, and the project ID of the victim: https://lookerstudio.google.com/reporting/create?c.reportId=<repordID-of-the-attacker-with-bigquery-queries>&ds.*.billingProjectId=victimsproject
  7. Visit the attacker’s website as the victim, and the victim’s billing will be exhausted by hundreds of BigQuery jobs

Disclosure Timeline

June 3, 2025 - Tenable reported the finding to Google, and Google acknowledges
June 16, 2025 - Tenable asks for updates
June 18, 2025 - Google assigns S2 severity
July 2, 2025 - Tenable asks for updates on this issue
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 updates that they are still working on the fix
July 31, 2025 - Tenable agrees to delay the disclosure date while Google is actively working
August 12, 2025 - Google says the engineering and product management teams are actively working to identify a mitigation that will balance both security and usability of the product
August 25, 2025 - Google updates that they have identified a solution
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-41
Credit:
Liv Matan
Affected Products:
GCP Looker Studio
Risk Factor:
Low

Advisory Timeline

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