Synopsis
Tenable Research has identified and responsibly disclosed a privilege escalation vulnerability in Looker. The flaw allowed an attacker with control over a Looker instance to abuse the trusted Looker service agent to execute unauthorized BigQuery jobs.
The vulnerability resides in Looker's SQL Runner feature, which is designed to execute SQL queries on a connected database. It was discovered that when running a query on a BigQuery resource, Looker's service agent (roles/looker.serviceAgent) is used. This service agent is configured with a wide range of permissions, including bigquery.jobs.create, bigquery.tables.create, and bigquery.tables.delete, enabling it to perform any BigQuery operation.
An attacker with access to the Looker instance's SQL Runner could exploit this by crafting and executing malicious SQL queries. This allowed them to bypass their own limited permissions and escalate privileges to those of the service agent, granting them full control over the connected BigQuery environment. This could lead to the creation, exfiltration, or deletion of sensitive data within the same project.
Solution
Google has fixed the issue.
Disclosure Timeline
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]