No workaround or mitigation is available.

VERSION SUGGESTED SOLUTION GlobalProtect App 6.3 on Windows Upgrade to 6.3.3 or later GlobalProtect App 6.2 on Windows Upgrade to 6.2.7-1077 or 6.2.8 or later GlobalProtect App 6.1 on Windows Upgrade to 6.2.8 or later or upgrade to 6.3.3 or later GlobalProtect App 6.0 on Windows Upgrade to 6.2.8 or later or upgrade to 6.3.3 or later GlobalProtect App on macOS No action needed GlobalProtect App on Linux No action needed GlobalProtect App on iOS No action needed GlobalProtect App on Android No action needed GlobalProtect UWP App No action needed

You can mitigate this issue for all platforms (Windows (https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/certifications/enable-and-verify-fips-cc-mode/enable-fips-cc-mode-using-the-windows-registry), macOS (https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/certifications/enable-and-verify-fips-cc-mode/enable-fips-cc-mode-using-the-macos-property-list), Linux (https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/certifications/enable-and-verify-fips-cc-mode/enable-fips-cc-mode-on-linux-endpoints-redhat), iOS (https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/certifications/enable-and-verify-fips-cc-mode/enable-and-verify-fips-cc-mode-using-workspaceone-on-ios-devices), Android (https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/certifications/enable-and-verify-fips-cc-mode/enable-and-verify-fips-cc-mode-using-microsoft-intune-on-android-endpoints)) by using the GlobalProtect app 6.0 in FIPS-CC mode or GlobalProtect app 5.1 in FIPS-CC mode. For details, refer to the first "FIPS-CC Certification Validation" table in our documentation (https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/certifications/resolve-fips-cc-mode-issues). Note: this is separate from any FIPS-CC configurations on any GlobalProtect portals or gateways. This workaround is specific to FIPS-CC mode on the GlobalProtect app. GlobalProtect portals or gateways do not need to use FIPS-CC mode as part of this workaround.

This issue is fixed in GlobalProtect app 6.2.1-c31 on Linux, GlobalProtect app 6.2.6 on Windows, GlobalProtect app 6.2.6-c857 on macOS, GlobalProtect app 6.3.2 on Windows and macOS, and all later GlobalProtect app versions. Additional fixes are under development and will be made available for the remaining platforms (Linux, iOS, and Android). The fix for this vulnerability requires three steps: 1. Ensure that all of your GlobalProtect portals use TLS certificate chains that meet the criteria specified in the "FIPS-CC Certification Validation" table in our documentation (https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/certifications/resolve-fips-cc-mode-issues). 2. Ensure that the TLS certificate chains used by the GlobalProtect portals are added to the root certificate store in your operating system. 3. Install a fixed version of GlobalProtect using one of the deployment options below. This setting enforces strict X.509v3 verification checks on the certificate provided by the GlobalProtect portal. Note: Prisma Access customers using portals with a *.gpcloudservice.com domain name already have valid TLS certificate chains. The root certificate for these portals is from GoDaddy, which is trusted by default in Windows, macOS, RHEL, Ubuntu, iOS, and Android. Therefore, Prisma Access customers using a GlobalProtect portal with a *.gpcloudservice.com domain name should only need to perform step 3 above. Important: If your GlobalProtect portals do not use valid X.509V3 TLS certificate chains, this will result in TLS verification failures. To generate a GlobalProtect portal certificate that can be used with a fixed version of GlobalProtect app, refer to the first "FIPS-CC Certification Validation" table in our documentation (https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/certifications/resolve-fips-cc-mode-issues). Warning: Performance Concern: Some customers reported problems connecting to Portals and Gateways when this solution was implemented in certain situations. This is due to certificate providers that rate limit requests for Online Certificate Status Protocol (OCSP) and certificate revocation list (CRL) checks. This happens when multiple users connect to GlobalProtect Portals from a single public IP (such as NAT) around the same time, such as when hundreds or thousands of end users connect around the start of a workday from a single office. Solution for new and existing GlobalProtect app >= 6.2.8 or GlobalProtect app >= 6.3.3 installations on Windows and macOS GlobalProtect 6.2.8 and GlobalProtect app 6.3.3 on Windows and macOS introduce a new configuration Enable Strict Certificate Check (https://docs.paloaltonetworks.com/globalprotect/6-2/globalprotect-app-release-notes/features-introduced-in-gp-app?otp=id_wvl_gwt_w2c#id_wvl_gwt_w2c) which enables certificate checks required to mitigate this issue on Windows and macOS.  This configuration only takes affect after the first connection between the GlobalProtect client and the GlobalProtect portal. Therefore the first connection is not protected. To ensure that the first connection is also protected, additionally follow the steps noted below for GlobalProtect < 6.2.8. This configuration option is currently not available for GlobalProtect app on platforms other than Windows and macOS. Solution for new and existing GlobalProtect app < 6.2.8 or GlobalProtect app < 6.3.3 installations on Windows Customers can use their endpoint mobile device management (MDM) tools to apply the following changes. 1. Install a fixed version of GlobalProtect app. 2. Update the following registry key with the specified recommended values (these values have the REG_SZ type): [HKEY_LOCAL_MACHINE\SOFTWARE\Palo Alto Networks\GlobalProtect\Settings] "cert-store"="machine" "cert-location"="ROOT" "full-chain-cert-verify"="yes" 3. To apply this registry change, restart Windows. Alternate solution for new GlobalProtect app < 6.2.8 or GlobalProtect app < 6.3.3 installations on Windows Install the GlobalProtect app with the pre-deployment key FULLCHAINCERTVERIFY set to Yes: > msiexec.exe /i GlobalProtect64.msi FULLCHAINCERTVERIFY="yes" Note: This command will add the registry values listed in the previous section (no additional MSI options are needed). Solution for new and existing GlobalProtect app < 6.2.8 or GlobalProtect app < 6.3.3 installations on macOS 1. Install a fixed version of the GlobalProtect app. 2. Use Xcode to edit the com.paloaltonetworks.GlobalProtect.settings.plist file (https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-apps/deploy-app-settings-transparently/deploy-app-settings-to-mac-endpoints/deploy-app-settings-in-the-mac-plist) in /Library/Preferences. 3. Add a "Settings" section if it does not exist within the GlobalProtect section. 4. Within the "Settings" section, add the full-chain-cert-verify key and set the string value to yes. <key>GlobalProtect</key> <dict>     (removed for brevity)     <key>Settings</key>     <dict>         <key>full-chain-cert-verify</key>         <string>yes</string>     </dict> </dict> 5. Restart macOS. Solution for new and existing GlobalProtect app installations on Linux 1. Create the /opt/paloaltonetworks/globalprotect/pangps.xml pre-deployment configuration file. 2. Add the pre-deployment settings to the pangps.xml file: <GlobalProtect>     <Settings>         <full-chain-cert-verify>yes</full-chain-cert-verify>     </Settings> </GlobalProtect> 3. Install a fixed version of GlobalProtect app. Solution for new and existing GlobalProtect app installations on Android and iOS Customers can use their endpoint mobile device management (MDM) tools to apply the following changes. 1. Set the key "full-chain-cert-verify"="yes".  2. Install a fixed version of GlobalProtect app for Android or iOS.