Vulnerabilities · 2022 · Google
CVE-2022-3421
Google Drive vulnerability
An attacker can pre-create the `/Applications/Google\ Drive.app/Contents/MacOS` directory which is expected to be owned by root to be owned by a non-root user. When the Drive for Desktop installer is run for the first time, it will place a binary in that directory with execute permissions and set its setuid bit. Since the attacker owns the directory, the attacker can replace the binary with a symlink, causing the installer to set the setuid bit on the symlink. When the symlink is executed, it will run with root permissions. We recommend upgrading past version 64.0
Affected products
Drive. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Google Drive runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
More vulnerabilities in Google products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.