Approved changes feed: RSS · Atom
cpe:2.3:a:google:drive:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Google (f181d1eb-7269-5bae-b76e-e66ceb214562) |
|---|---|
| Product | Drive (3e328298-5eaa-5d50-83d1-8bbaaafa78dc) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-3421 |
vulnerable | 2026-06-08 05:48:20.905157 |
Privilege escalation in Google Drive for Desktop on MacOS
MEDIUM (5.6)
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: 2022-10-17T00:00:00.000Z
Updated: 2025-04-21T13:47:49.429Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.