{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-3421 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-3421 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-3421 is a medium-severity vulnerability in Google LLC Drive for Desktop MacOS, published on 17 Oct 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-3421 and fix it if it is affected.\n\nWhat it is: CVE-2022-3421 is a medium-severity vulnerability in Google LLC Drive for Desktop MacOS, published on 17 Oct 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-3421 in the wild and no public exploit code.\n\nAffected product: Google LLC Drive for Desktop MacOS. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-3421/ (Markdown: https://insights.sbomify.com/CVE-2022-3421/index.md)","id":"CVE-2022-3421","markdown":"https://insights.sbomify.com/CVE-2022-3421/index.md","name":"CVE-2022-3421","record":{"aliases":["GHSA-g3jf-h663-mqrx"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Google Drive for Desktop","requires_auth":"low_privilege","summary":"An attacker can escalate privileges to root by manipulating directory ownership and symlinks during the initial installation of Google Drive for Desktop on macOS.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"drive","vendor":"google"}],"cvss":{"score":5.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"},{"id":"CWE-264","name":null}],"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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in Google Drive for Desktop on MacOS","id":"CVE-2022-3421","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Privilege Management in tooljet/tooljet","id":"CVE-2022-3422"},"packages":[],"prev":{"headline":"Official Integration for Billingo \u003c 3.4.0 - ShopManager+ Stored XSS","id":"CVE-2022-3420"},"products":["Drive for Desktop MacOS"],"published":"2022-10-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-21","vendors":["Google LLC"]},"summary":"An attacker can escalate privileges to root by manipulating directory ownership and symlinks during the initial installation of Google Drive for Desktop on macOS.","url":"https://insights.sbomify.com/CVE-2022-3421/"}