Vulnerability Description
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
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Drive | < 64.0 | |
| Apple | Macos | - |
Related Weaknesses (CWE)
References
- https://support.google.com/a/answer/7577057?hl=enRelease NotesVendor Advisory
- https://support.google.com/a/answer/7577057?hl=enRelease NotesVendor Advisory
FAQ
What is CVE-2022-3421?
CVE-2022-3421 is a vulnerability with a CVSS score of 5.6 (MEDIUM). 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 ...
How severe is CVE-2022-3421?
CVE-2022-3421 has been rated MEDIUM with a CVSS base score of 5.6/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-3421?
Check the references section above for vendor advisories and patch information. Affected products include: Google Drive, Apple Macos.