229 lines
9.1 KiB
Markdown
229 lines
9.1 KiB
Markdown
---
|
||
type: Addressed
|
||
product: GlobalProtect
|
||
version: 6.2.8
|
||
---
|
||
|
||
## GPC-22894
|
||
|
||
Fixed an issue where GlobapProtect did not detect the correct version of Kaspersky Endpoint Security.
|
||
|
||
## GPC-22847
|
||
|
||
Fixed an issue where GlobalProtect did not detect Qualys for patch management.
|
||
|
||
## GPC-22764
|
||
|
||
Fixed an issue where wa_3rd_party_host_xx.exe attempted to connect to Microsoft’s update servers for information and the patch information was not sent in the HIP report. This occured even though HIP Exceptions for patch management were configured to exclude Windows updates agent.
|
||
|
||
## GPC-22740
|
||
|
||
Fixed an issue where macOS computers displayed both the new and old versions of the GlobalProtect welcome page.
|
||
|
||
## GPC-22688
|
||
|
||
Fixed an issue for proxy-only mode where customers were unable to access websites when the computer woke up from sleep.
|
||
|
||
## GPC-22638
|
||
|
||
Fixed an issue where Global Protect HIP did not detect the drive state when using Trellix Drive Encryption 8.0.
|
||
|
||
## GPC-22620
|
||
|
||
Fixed an issue where GlobalProtect was not working correctly and blocked internet access.
|
||
|
||
## GPC-22589
|
||
|
||
Fixed an issue where the Report an Issue functionality did not send the troubleshooting log to the administrator’s Strata Logging Service instance.
|
||
|
||
## GPC-22544
|
||
|
||
Fixed an issue where the GlobalProtect client did not send the HIP report causing user-IP mapping to be cleared and resulting in traffic drop.
|
||
|
||
## GPC-22542
|
||
|
||
Fixed an issue where the embedded browser shown as part of SAML authentication was blank.
|
||
|
||
## GPC-22487
|
||
|
||
Fixed an issue where Norton 360 was not compatible with GlobalProtect causing the device to fail the HIP check.
|
||
|
||
## GPC-22443
|
||
|
||
Fixed an issue where the GlobalProtect agent showed as connected even when the virtual adapter was down.
|
||
|
||
## GPC-22437
|
||
|
||
Fixed an issue where the GlobalProtect macOS client experienced a keep-alive timeout, preventing the tunnel from connecting.
|
||
|
||
## GPC-22412
|
||
|
||
Fixed an error where virtual adapter is not set correctly during tunnel creation.
|
||
|
||
## GPC-22297
|
||
|
||
Fixed an issue where the Customer was getting "A valid client certificate is required for authentication" even though they had a valid client certificate installed. In order to access the fix, you must do one of the following:
|
||
|
||
- uninstall the previous release (to remove all registry entries).
|
||
- manually delete the registry value "ext-key-usage-oid-for-client-cert" under "HKEY_LOCAL_MACHINE\SOFTWARE\Palo Alto Networks\GlobalProtect\Settings" as it may contain a corrupted value.
|
||
|
||
## GPC-22264
|
||
|
||
Fixed an issue where the GlobalProtect HIP report did not detect the last full scan time for Avast antivirus software.
|
||
|
||
## GPC-22245
|
||
|
||
Fixed an issue where transparent upgrade from GlobalProtect version 6.2.4 or 6.2.5 to version 6.2.6 failed on some Windows endpoints with error 1618.
|
||
|
||
## GPC-22237
|
||
|
||
Fixed an issue where GlobalProtect shut down unexpectedly on Windows 11 devices running multiple versions of GlobalProtect 6.3. The issue was caused by the firewall sending invalid IPv6 packets to GlobalProtect, which did not have a validation method before processing.
|
||
|
||
## GPC-22235
|
||
|
||
Fixed an issue where users were unable to connect to the app after the system woke up from sleep mode.
|
||
|
||
## GPC-22233
|
||
|
||
Fixed an issue where the users were unable to connect the GlobalProtect app after performing the resolution of CVE-2024-5921. The app displayed the following error, “The certificate CN name mismatch.”
|
||
|
||
## GPC-22126
|
||
|
||
Fixed an issue where GlobalProtect version 6.2.6-838 was stuck intermittently during the connection process.
|
||
|
||
## GPC-22123
|
||
|
||
Fixed an issue where the GlobalProtect app got stuck and users faced connection issues after the system woke up from sleep mode even though the internet connection was stable.
|
||
|
||
## GPC-22092
|
||
|
||
Fixed an issue where the GlobalProtect app failed to validate the server certificate when the portal or gateway sent only the leaf certificate.
|
||
|
||
## GPC-22061
|
||
|
||
Fixed an issue where the GlobalProtect client displayed an error when using an ECDSA certificate with explicit EC parameters in FIPS mode.
|
||
|
||
## GPC-22043
|
||
|
||
Fixed an issue where Okta push notification shows incorrect Windows OS, when Okta SAML authentication is enabled in GlobalProtect.
|
||
|
||
## GPC-22036
|
||
|
||
Resolved an issue where GlobalProtect did not populate the internal routes in the user's routing table.
|
||
|
||
## GPC-22028
|
||
|
||
Fixed an issue where the disconnect reason for macOS users was getting cached.
|
||
|
||
## GPC-21988
|
||
|
||
Fixed an issue where the GlobalProtect Client displayed a download prompt or was updated even with an "upgrade disallow" configuration.
|
||
|
||
## GPC-21979
|
||
|
||
Fixed an issue where the included domain traffic was routed through the physical interface when split tunnel was configured.
|
||
|
||
## GPC-21961
|
||
|
||
Fixed an issue where, after upgrading to GlobalProtect version 6.2.5, the app triggered authentication and opened multiple browser tabs when the computer woke from sleep.
|
||
|
||
## GPC-21960
|
||
|
||
Fixed an issue where the HIP check failed to detect the Norton anti-malware version 24.11.9615.0.
|
||
|
||
## GPC-21955
|
||
|
||
Fixed an issue where the HIP notification pop-up on macOS looked different from that on Windows.
|
||
|
||
## GPC-21938
|
||
|
||
Fixed an issue where, when the GlobalProtect app version 6.3.x was installed on devices running macOS, the HIP check failed to detect ESET Endpoint Security version 8.
|
||
|
||
## GPC-21918
|
||
|
||
Fixed an issue where, when the patch management category was excluded for HIP checks, HIP checks were still happening for missing patches which consumed CPU resources on users' machine.
|
||
|
||
## GPC-21938
|
||
|
||
Fixed an issue where, when the GlobalProtect app version 6.3.x was installed on devices running macOS, the HIP check failed to detect ESET Endpoint Security version 8.
|
||
|
||
## GPC-21775
|
||
|
||
Fixed an issue where GlobalProtect users on macOS were disconnected immediately after sending the HIP report.
|
||
|
||
## GPC-21771
|
||
|
||
Fixed an issue where the GlobalProtect HIP check incorrectly detected Malware Definition Date for Trend Micro Deep Security Agent, which caused the device to fail the HIP check.
|
||
|
||
## GPC-21743
|
||
|
||
Fixed an issue where a user was randomly prompted with a \"Login Successful\" message when connecting to GlobalProtect (GP), even though GP was not connected.
|
||
|
||
## GPC-21695
|
||
|
||
Fixed an issue where the GlobalProtect embedded browser could not utilize a new PIV certificate for SAML authentication if multiple certificates were available.
|
||
|
||
## GPC-21677
|
||
|
||
Fixed an issue where GlobalProtect configured for Always-on Pre-logon may not display the captive portal page if there is a delay with network access or Internet connectivity.
|
||
|
||
## GPC-21653
|
||
|
||
Fixed an issue where the GlobalProtect virtual adapter was not set up correctly.
|
||
|
||
## GPC-21639
|
||
|
||
Fixed an issue where the GlobalProtect macOS client did not extend the session even though the user clicked the Extend Session button.
|
||
|
||
## GPC-21627
|
||
|
||
Fixed an issue where the Report an Issue feature failed to work for a specific user whose username contained Japanese character.
|
||
|
||
## GPC-21615
|
||
|
||
Fixed an issue where the GlobalProtect agent (wa_3rd_party_host_64.exe) modified the __PSLockDownPolicy registry key from 4 (secure language mode) to 0 (full language mode) after a reboot.
|
||
|
||
## GPC-21571
|
||
|
||
Fixed an issue where the hyperlink in HIP notification opened up in Webview2 instead of the default browser.
|
||
|
||
## GPC-21565
|
||
|
||
Fixed an issue where the SAML embedded browser did not remember the username after sign-out, even when the user had selected the check box “Remember Me" on the SAML embedded browser,
|
||
|
||
## GPC-21527
|
||
|
||
Fixed an issue where the firewall did not exclude the APIPA (169.254.0.0/16) range from GlobalProtect when the Endpoint Traffic Policy Enforcement feature was enabled with the exclude option. As a result, traffic to the APIPA range was sent over GlobalProtect instead of the local interface.
|
||
|
||
## GPC-21467
|
||
|
||
Fixed an issue where the Transparent Upgrade with Proxy only mode did not work as expected and no tunnel was established with the gateway.
|
||
|
||
## GPC-21453
|
||
|
||
Fixed an issue where the GlobalProtect app window displayed "static" instead of the connected gateway name.
|
||
|
||
## GPC-21222
|
||
|
||
Fixed an issue where the GlobalProtect HIP check incorrectly detected the Real Time Protection Status and Last Full Scan for Avast application, which caused the device to fail the HIP check.
|
||
|
||
## GPC-21090
|
||
|
||
Fixed an issue where GlobalProtect only displayed ADEM information for approximately 120 users even though more than 600 ADEM users were connected to GlobalProtect.
|
||
|
||
## GPC-20967
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed with the Conditional Connect method, users had to click the Connect button twice to connect to an external gateway after a system reboot.
|
||
|
||
## GPC-20632
|
||
|
||
Fixed an issue where GLobalProtect was stuck in connecting mode after the customer manually selected a gateway that hit the maximum user limit. This was a multi-gateway environment with SAML/CAS authentication method.
|
||
|
||
## GPC-20621
|
||
|
||
Fixed an issue where users from overseas locations were disconnected from GlobalProtect due to the HIP report not being sent with manual gateway selection.
|
||
|
||
## GPC-18587
|
||
|
||
Fixed an issue where, when the GlobalProtect was installed on Windows devices and Connect Before Logon was deployed, users were unable to log in to the device using the User Principal Name (UPN). This issue occurred when the GlobalProtect credential provider was selected and the device was offline.
|