Privilege escalation in Google Drive
CVE-2022-3421
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
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.6 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L.
EPSS exploit prediction
EPSS 0.001, 2.6th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Google Drive
- Google Llc Drive For Desktop macOS — versions unspecified
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (ARPSyndicate/cvemon, kohnakagawa/kohnakagawa). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- support.google.com/a/answer/7577057 (Release Notes, Vendor Advisory)