CVE-2025-2183 GlobalProtect App: Improper Certificate Validation Leads to Privilege Escalation
🔗 CVE IDs covered (1)
📋 Description
An insufficient certificate validation issue in the Palo Alto Networks GlobalProtect™ app enables attackers to connect the GlobalProtect app to arbitrary servers. This can enable a local non-administrative operating system user or an attacker on the same subnet to install malicious root certificates on the endpoint and subsequently install malicious software signed by the malicious root certificates on that endpoint.
🎯 Affected products2
- GlobalProtect App
- GlobalProtect UWP App
✅ Remediation
VERSION MINOR VERSION SUGGESTED SOLUTION GlobalProtect App 6.3 on Windows 6.3.0 through 6.3.2 Upgrade to 6.3.2-h9 or 6.3.3-h2 or later*. GlobalProtect App 6.2 on Windows 6.2.0 through 6.2.8 Upgrade to 6.2.8-h3 or later*. GlobalProtect App 6.1 on Windows Upgrade to 6.2.8-h3 or 6.3.3-h2 or later*. GlobalProtect App 6.0 on Windows Upgrade to 6.2.8-h3 or 6.3.3-h2 or later*. GlobalProtect App 6.3 on Linux 6.3.0 through 6.3.2 Upgrade to 6.3.3 or later*. GlobalProtect App 6.2 on Linux Upgrade to 6.3.3 or later*. GlobalProtect App 6.1 on Linux Upgrade to 6.3.3 or later*. GlobalProtect App 6.0 on Linux Upgrade to 6.3.3 or later*. GlobalProtect App on Android, iOS, macOS No action needed. GlobalProtect UWP App No action needed. * In addition to the software updates listed above, additional steps are required to protect against this vulnerability as described below: Solution for new and existing GlobalProtect app installation on Windows / Linux 1. Ensure the portal/gateway certificate can be validated using the operating system's certificate store (e.g., Local Machine Certificate Store or Current User Certificate Store in Windows; for Linux, refer to this documentation (https://docs.paloaltonetworks.com/globalprotect/6-2/globalprotect-app-user-guide/globalprotect-app-for-linux/support-for-native-certificate-store-for-prisma-access-and-globalprotect-app)). 2. Remove any certificates associated with portal/gateway validation from the "Trusted Root CA" list on the Portal. 3. Enable portal setting: “Enable Strict Certificate Check” (set FULLCHAINCERTVERIFY to yes). Workarounds and mitigations: No known workarounds exist for this issue.