SQL Injection in Looker Project Generation Endpoint Allows Access to Internal MySQL Database
Google Cloud Looker
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Google Cloud Looker Looker-hosted |
| No fix yet |
| Google Cloud Looker Self-hosted |
|
Google Cloud Looker
| Product | Affected | Fixed in |
|---|---|---|
| Google Cloud Looker Looker-hosted |
| No fix yet |
| Google Cloud Looker Self-hosted |
|
< 24.18.198< 25.0.75< 25.6.63< 25.8.45< 25.10.33| No fix yet |
The Looker endpoint for generating new projects from database connections allows users to specify "looker" as a connection name, which is a reserved internal name for Looker's internal MySQL database. The schemas parameter is vulnerable to SQL injection, enabling attackers to manipulate SELECT queries that are constructed and executed against the internal MySQL database. This vulnerability allows users with developer permissions to extract data from Looker's internal MySQL database.
Looker-hosted and Self-hosted were found to be vulnerable. This issue has already been mitigated for Looker-hosted instances. No user action is required for these.
Self-hosted instances must be upgraded as soon as possible. This vulnerability has been patched in all supported versions of Self-hosted. The versions below have all been updated to protect against this vulnerability. You can download these versions at the Looker download page https://download.looker.com/ : * 24.12.106 * 24.18.198+ * 25.0.75 * 25.6.63+ * 25.8.45+ * 25.10.33+ * 25.12.1+ * 25.14+
From the CVE record · GoogleCloud
The endpoint for creating projects from database connections has a SQL injection flaw in its schemas parameter when users specify the reserved “looker” connection name. Users with developer permissions can manipulate queries against Looker’s internal MySQL database and extract data. Both Looker-hosted and self-hosted instances were affected, but Looker-hosted instances have already been mitigated.
Operators of self-hosted Google Cloud Looker should check their versions; Looker-hosted operators need no action.