Remote Code Execution in Looker due to Improperly Validated Directory Deletion
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.195< 25.0.72< 25.6.60< 25.8.42< 25.10.22| No fix yet |
An attacker with a Looker Developer role could manipulate a LookML project to exploit a race condition during Git directory deletion, leading to arbitrary command execution on the Looker instance.
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.103+ * 24.18.195+ * 25.0.72+ * 25.6.60+ * 25.8.42+ * 25.10.22+
From the CVE record · GoogleCloud
Google Cloud Looker has a race condition during Git directory deletion. An attacker with a Looker Developer role can manipulate a LookML project to execute arbitrary commands on the Looker instance. Both Looker-hosted and Self-hosted instances were affected; Looker-hosted instances have already been mitigated.
Operators of Self-hosted Google Cloud Looker should check their versions; Looker-hosted instances require no user action.