CVE-2024-32813 – WordPress Integrate Google Drive plugin <= 1.3.9 - Broken Access Control vulnerability
https://notcve.org/view.php?id=CVE-2024-32813
Missing Authorization vulnerability in SoftLab Integrate Google Drive.This issue affects Integrate Google Drive: from n/a through 1.3.9. Vulnerabilidad de falta de autorización en SoftLab Integrate Google Drive. Este problema afecta a Integrate Google Drive: desde n/a hasta 1.3.9. The Integrate Google Drive plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on several functions in versions up to, and including, 1.3.9. This makes it possible for unauthenticated attackers to perform unauthorized actions. • https://patchstack.com/database/vulnerability/integrate-google-drive/wordpress-integrate-google-drive-plugin-1-3-9-broken-access-control-vulnerability?_s_id=cve • CWE-862: Missing Authorization •
CVE-2024-32949 – Integrate Google Drive <= 1.3.8 - Missing Authorization
https://notcve.org/view.php?id=CVE-2024-32949
The Integrate Google Drive plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on several functions in versions up to, and including, 1.3.8. This makes it possible for unauthenticated attackers to perform unauthorized actions. • CWE-862: Missing Authorization •
CVE-2023-32117 – Integrate Google Drive <= 1.1.99 - Missing Authorization via REST API Endpoints
https://notcve.org/view.php?id=CVE-2023-32117
The Integrate Google Drive plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on several REST API endpoints in versions up to, and including, 1.1.99. This makes it possible for unauthenticated attackers to perform a wide variety of operations, such as moving files, creating folders, copying details, and much more. • https://github.com/RandomRobbieBF/CVE-2023-32117 • CWE-862: Missing Authorization •
CVE-2022-3421 – Privilege escalation in Google Drive for Desktop on MacOS
https://notcve.org/view.php?id=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 Un atacante puede pre crear el directorio "/Applications/Google\ Drive.app/Contents/MacOS" que es esperado que sea propiedad de root para que sea propiedad de un usuario no root. • https://support.google.com/a/answer/7577057?hl=en • CWE-264: Permissions, Privileges, and Access Controls CWE-269: Improper Privilege Management •