Command Injection in Looker
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.192< 25.0.69< 25.6.57< 25.8.39< 25.10.22| No fix yet |
A Command Injection vulnerability, resulting from improper file path sanitization (Directory Traversal) in Looker allows an attacker with Developer permission to execute arbitrary shell commands when a user is deleted on the host system.
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.100+ * 24.18.192+ * 25.0.69+ * 25.6.57+ * 25.8.39+ * 25.10.22+
From the CVE record · GoogleCloud
Improper file path sanitization in Looker can allow an attacker with Developer permission to execute arbitrary shell commands on the host system when a user is deleted. 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 whether their installation is below a patched release in its supported version line.