Fixed an issue where, when the GlobalProtect app was installed on Linux devices for the first time, the users were prompted to enter the user credentials twice.

Fixed an issue where the GlobalProtect app got randomly disconnected when there was a high amount of traffic like when running a speed test or using Zoom or Hangout.

A fix was made to address an OpenSSL infinite loop vulnerability in GlobalProtect app software (CVE-2022-0778).

Fixed an issue where, when the GlobalProtect app was installed on macOS devices, the connection became unstable when the user clicked the

Click here

or

Retry

button on the default browser page for SAML authentication.

Fixed an issue where, when the GlobalProtect app was installed on the Linux devices, the app could not resolve internal domains when the DNS suffix was not configured.

Fixed an issue where, when the GlobalProtect app was installed on Linux devices, the GlobalProtect logs displayed password information when the password contained the (<) character. The password characters succeeding the (<) character were displayed in the logs.

Fixed an issue where, when the GlobalProtect app was installed on macOS devices, the GlobalProtect app tried to restore the gateway connection even when the device was on Modern Standby mode. The users were prompted to authenticate using multi-factor authentication (MFA) authentication.

Fixed an issue where, when the GlobalProtect app was installed and configured with

Allow User to Disable GlobalProtect

to

Allow with Ticket

option, the app did not display the

Need Help?

link next to the

Ticket Number

field on the screen.

Fixed an issue where, when Connect Before Logon using Security Assertion Markup Language (SAML) authentication was used to login to the endpoint, the users could not authenticate as the authentication process stopped when redirected to the organization’s sign-in page.

Fixed an issue where, when the GlobalProtect app was installed on Windows devices, the machine displayed a blue screen when the users tried to connect to the GlobalProtect app.

Fixed an issue where the GlobalProtect IPV6 static route for the gateway was getting removed shortly after establishing the connection causing unexpected GlobalProtect disconnections.

Fixed an issue where, when the GlobalProtect app was deployed for pre-logon, the GlobalProtect Enforcer remained enabled even after the app was disabled.

Fixed an issue where the HIP check did not detect the Sentinel One RTP and definition date properly, which caused the device to fail the HIP check.

Fixed an issue, where the GlobalProtect app users were prompted to re-enter the password when the connection was refreshed.This issue occurred only when the password contained non-English alphabets.

Fixed an issue where, when the GlobalProtect app was installed on Windows devices and split tunnel was configured to exclude or include any application traffic that relied on the loopback connection source IP address, the split tunnel configuration based on the application did not work.

Fixed an issue where the GlobalProtect app did not detect real-time protection for SentinelOne Endpoint Security, which caused the device to fail the HIP check.

Fixed an issue where the TCP Option lookup for IP fragmented TCP packets caused the endpoint to lose access to internal resources.

Fixed an issue where, when the IPv6 Sinkhole feature was enabled to block the GlobalProtect app from accessing the local network devices using IPv6 address, the GlobalProtect gateway still allowed the GlobalProtect app to send IPV6 traffic to local network devices instead of blocking them.

Fixed an issue where macOS devices were able to bypass the GlobalProtect tunnel using the physical adapter even when

No direct access to local network

was enabled.

Fixed an issue where, when the GlobalProtect app was installed on macOS devices, the GlobalProtect HIP report displayed encryption status even when the encryption feature was disabled.

Fixed an issue where the

Check for Updates

option in the GlobalProtect app failed to display the recent GlobalProtect version available for update. The users had to refresh the GlobalProtect connection to get the latest version updates.

Fixed an issue where the GlobalProtect HIP report displayed incorrect OS version Windows 10 instead of the correct version Windows 11.

Fixed an issue where, when the split tunnel was configured on the GlobalProtect gateway to include routes, the traffic which was not included was also sent over the VPN tunnel intermittently.

Fixed an issue where, when the GlobalProtect app was installed on macOS devices, the HIP match logs were missing for some user profiles which caused the device to fail the HIP check.

Fixed an issue where after a GlobalProtect connection was established, the network interface was detected as public instead of domain due to timer issue with Network Location Awareness (NLA).

When connected to GlobalProtect with

Resolve All FQDNs Using DNS Servers Assigned by the Tunnel (Windows Only)

set to

Yes

in the App Configurations area of the GlobalProtect portal configuration, performance is slow in the Windows Active Directory Users and Computers console.

Workaround:

Set

Resolve All FQDNs Using DNS Servers Assigned by the Tunnel (Windows Only)

to

No

.

Fixed an issue where the DNS UDP checksum was incorrectly calculated by GlobalProtect, causing slow connections when the user accessed internal applications using either the CLI or web browser.

Fixed an issue where DNS queries for excluded domains were sent out on both the GlobalProtect app virtual adapter and the device's physical adapter with the

Split-Tunnel Option

set to

Both Network Traffic and DNS

in the App Configurations area of the GlobalProtect portal configuration.

Fixed an issue where the DNS UDP checksum was incorrectly calculated, causing latency in the GlobalProtect connection.

Fixed an issue where, when the

Resolve All FQDNs using DNS Servers Assigned by the Tunnel (Windows Only)

option was enabled in the App Configurations area of the GlobalProtect portal configuration, GlobalProtect generated a negative DNS response incorrectly using ‘SERVERFAIL’ as the error code, causing DNS resolution to fail and delays on application start-up on end points in a dual stack environment.

Fixed an issue where, if GlobalProtect was configured for domain-based split tunneling and the domain name resolved to the loopback address (127.0.0.1), the GlobalProtect app would disconnect on devices running macOS 11.5 or later.

Fixed an issue where, when the

Resolve All FQDNs using DNS Servers Assigned by the Tunnel (Windows Only)

option in the App Configurations area of the GlobalProtect portal configuration was enabled, the GlobalProtect pre-logon process took more than 2 minutes to complete when the user tried to log on to the Windows operating system after a reboot.

Fixed an issue where, after an upgrade, GlobalProtect generated a negative DNS response incorrectly using error code 'SERVERFAIL', which caused Kerberos authentication to fail.

Fixed an issue where the GlobalProtect tunnel could not send traffic after the system woke up from sleep mode.