Remote Command Execution in Looker via IBM DB2 JDBC drive
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 |
|
< 25.12.42< 25.14.50< 25.16.44| No fix yet |
A Looker user with a Developer role could create a database connection using IBM DB2 driver and, by manipulating LookML, cause Looker to execute a malicious command, due to inadequate filtering of the driver's 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/ : * 25.0.93+ * 25.6.84+
* 25.12.42+ * 25.14.50+ * 25.16.44+
From the CVE record · GoogleCloud
Inadequate filtering of IBM DB2 driver parameters affects Looker-hosted and Self-hosted instances. A Looker user with a Developer role who can create a database connection can manipulate LookML to cause Looker to execute a malicious command. Looker-hosted instances have already been mitigated.
Operators of Self-hosted Google Cloud Looker should check their installations; the affected version range was not specified.