A security-related fix was made to prevent a memory corruption vulnerability in PAN-OS® software (PAN-SA-2019-0023 / CVE-2019-1582).

A security-related fix was made to prevent a memory corruption vulnerability in PAN-OS software (PAN-SA-2019-0021 / CVE-2019-1580).

Fixed CVE-2019-1581, see PAN-SA-2019-0022 for details.

Fixed an issue where the

Wildfire Analysis Report

incorrectly displayed the following error message:

You are not authorized to access thispage on the web interface

.

(

Virtual and M-Series Panorama appliances and Log Collectors only

) Fixed an issue where closed Elasticsearch (ES) indices were continuing to receive and re-queue logs, which resulted in high CPU usage.

Fixed an issue where the GTP-U session did not match the correct policy, which caused the IMSI and IMEI not to display in the inner session traffic and threat logs.

(

GlobalProtect™ Clientless VPN environments only

) Fixed an issue where a process (all_pktproc) stopped responding and caused the firewall to restart unexpectedly when processing GlobalProtect Clientless VPN traffic. To leverage this fix, you must first upgrade (

Devices

Dynamic Updates

) to GlobalProtect Clientless VPN content release 79 or a later release.

Fixed an issue where firewall logs incorrectly included the end-user IP address in GTP message logs when you configured PAA IE with IPv4 and IPv6 dual stack in the Create Session Response message.

Fixed an issue where the firewall dropped GTPv1

DELETE PDP

response packets that had a termination endpoint ID (TEID) value of 0.

Fixed an issue where forward error correction (FEC) was disabled by default for AOC modules, which caused QSFP ports to flap or remain in the

DOWN

state. With this fix, FEC is enabled by default for AOC modules.

Fixed an issue on a firewall where stateful inspection failed, which caused the firewall to drop GTPv2-C Modify Bearer Request packets.

(

Virtual and M-Series Panorama appliances and Log Collectors only

) Fixed an issue where a Log Collector received logs destined for closed ES indices, which caused indices to return failure messages and, when the issue persisted for more than a few hours, caused Log Collectors to disconnect and reconnect repeatedly when attempting (and failing) to process the re-queued logs.