Looker account compromise via punycode homograph attack
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.193< 25.0.69< 25.6.57< 25.8.39< 25.10.22| No fix yet |
An attacker could take over a Looker account in a Looker instance configured with OIDC authentication, due to email address string normalization.Looker-hosted and Self-hosted were found to be vulnerable.
This issue has already been mitigated for Looker-hosted.
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.193+ * 25.0.69+ * 25.6.57+ * 25.8.39+ * 25.10.22+ * 25.12.0+
From the CVE record · GoogleCloud
Email address string normalization can allow an attacker to take over an account in a Looker instance configured with OIDC authentication. Both Looker-hosted and Self-hosted instances were affected; the input does not specify whether the attack requires authentication or user interaction.
Operators of Looker-hosted or Self-hosted Google Cloud Looker instances configured with OIDC authentication should check their deployments; affected version ranges are not specified.