Remote Command Execution in Looker via IBM DB2 JDBC drive
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 25.0.93, 25.12.42, 25.14.50 and 2 more.
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+
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Google Cloud | <25.0.93, <25.12.42, <25.14.50, <25.16.44, <25.6.84 | 25.0.93, 25.12.42, 25.14.50, 25.16.44, 25.6.84 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket