Addressed Issues in GlobalProtect App 6.0
See the list of addressed issues in GlobalProtect app
6.0 for Android, iOS, Chrome, Windows, Windows 10 UWP, macOS, and Linux.
The following topic describes the issues addressed in
GlobalProtect 6.0 for Android, iOS, Chrome, Windows, Windows 10
UWP, macOS, and Linux.
GlobalProtect App 6.0.1 Addressed Issues
The following table lists the issues that are addressed
in GlobalProtect app 6.0.1 for macOS, Windows, and Linux.
Issue ID | Description |
---|---|
GPC-15293 | 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. |
GPC-15075 | 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. |
GPC-15068 | A fix was made to address an OpenSSL infinite
loop vulnerability in GlobalProtect app software (CVE-2022-0778). |
GPC-15062 | 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. |
GPC-15060 | 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. |
GPC-14959 | 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. |
GPC-14824 | 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. |
GPC-14804 | 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. |
GPC-14792 | 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. |
GPC-14763 | 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. |
GPC-14691 | Fixed an issue where the GlobalProtect IPV6
static route for the gateway was getting removed shortly after establishing
the connection causing unexpected GlobalProtect disconnections. |
GPC-14640 | Fixed an issue where, when the GlobalProtect
app was deployed for pre-logon, the GlobalProtect Enforcer remained enabled
even after the app was disabled. |
GPC-14609 | 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. |
GPC-14572 | 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. |
GPC-14492 | 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. |
GPC-14477 | 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. |
GPC-14453 | Fixed an issue where the TCP Option lookup
for IP fragmented TCP packets caused the endpoint to lose access
to internal resources. |
GPC-14405 | 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. |
GPC-14329 | 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. |
GPC-14278 | 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. |
GPC-14276 | 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. |
GPC-14251 | Fixed an issue where the GlobalProtect HIP
report displayed incorrect OS version Windows 10 instead of the
correct version Windows 11. |
GPC-14100 | 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. |
GPC-14010 | 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. |
GPC-14008 | 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). |
GPC-13998 | 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 . |
GPC-13986 | 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. |
GPC-13970 | 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. |
GPC-13963 | Fixed an issue where the DNS UDP checksum
was incorrectly calculated, causing latency in the GlobalProtect connection. |
GPC-13900 | 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. |
GPC-13857 | 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. |
GPC-13819 | 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. |
GPC-13801 | Fixed an issue where, after an upgrade,
GlobalProtect generated a negative DNS response incorrectly using
error code 'SERVERFAIL', which caused Kerberos authentication to
fail. |
GPC-13774 | Fixed an issue where the GlobalProtect tunnel
could not send traffic after the system woke up from sleep mode. |
GPC-13725 | Fixed an issue where, during a transparent
upgrade of the GlobalProtect app, the system rebooted or woke up
from hibernation, which caused the upgrade to fail due to competing resources
between the system reboot and transparent upgrade. The previous
version of the GlobalProtect app was completely uninstalled. |
GlobalProtect
App 6.0.1 Addressed Issues (Android)
The following table lists the issues that are addressed
in GlobalProtect app 6.0.1 for Android.
Issue ID | Description |
---|---|
GPC-14612 | Fixed an issue where, on Android devices
with the GlobalProtect app installed, when the client certificate
alias setting was set to pre-select in the managed configuration,
the GlobalProtect Choose certificate pop-up
failed to appear and the user was redirected to the captive portal
(SAML) login page. |
GlobalProtect App 6.0.0 Addressed Issues
There are no addressed issues in the 6.0.0 release.
Recommended For You
Recommended Videos
Recommended videos not found.