Remote Code Execution in Looker via Teradata JDBC Driver
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.200< 25.0.78< 25.6.65< 25.8.47< 25.12.10| No fix yet |
A Looker user with a Developer role could cause Looker to execute a malicious command, due to insecure processing of Teradata driver parameters.
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 from this vulnerability. You can download these versions at the Looker download page https://download.looker.com/ : * 24.12.108+ * 24.18.200+ * 25.0.78+ * 25.6.65+ * 25.8.47+ * 25.12.10+ * 25.14+
From the CVE record · GoogleCloud
Insecure processing of Teradata driver parameters in Google Cloud Looker could let a user with the Developer role cause Looker to execute a malicious command. Both Looker-hosted and Self-hosted instances were affected; Looker-hosted instances have already been mitigated and require no user action.
Operators of Self-hosted Google Cloud Looker should check their versions; the issue is patched in all supported versions at the listed fixed releases.