Fixed Issues and Other Changes
The following table lists issues that have been fixed and are resolved by upgrading to this release.
Report Number |
Description |
Installation and Upgrading |
|
VTM-45019 |
Fixed an issue which could lead to rejection of self-signed admin SSL certificate by prospective clients because of absence of subject alternative name extension in the certificate. |
Administrative Server |
|
VTM-45124 |
Fixed an issue where the 'adminport' setting could not be changed using the Admin UI. |
VTM-41382 |
Added X-Content-Type-Options: nosniff header in all responses for the admin server UI to enable the additional security protection measures in user agent where they are supported. |
SOAP API |
|
VTM-45015 |
The version of the expat XML parser library used in the Administration Server has been increased to 2.4.1. |
Connection Processing |
|
VTM-45092 |
Fixed an issue where the 'max_connections_pernode' setting could cause some requests to wait for longer than needed to restrict the number of connections to nodes. |
Pools |
|
VTM-45234 |
Fixed an issue when setting max_connections_per_node, could cause a child process crash when a request is made to a pool with no working nodes. |
VTM-45113 |
Fixed an issue where the connection/transaction counters for a draining pool node could fail to decrease when a connection/transaction to a pool node is closed/completed. If the node was then reactivated the discrepancy in the counters could cause the traffic manager to cap the number of connections/transactions to the pool node to be much less than the configuration max_connections_pernode or max_transactions_per_node. |
Fault Tolerance |
|
VTM-19838, |
Fixed an issue where vTM doesn't honor the flipper!use_bindip setting for binding the flipper port to a single IP Address following a software restart. |
Service Protection |
|
VTM-45147 |
Fixed an issue that a client can establish more than max_1_connections connections to the vTM once some HTTP/1.x connections from the same client have been rejected due to being capped by max_1_connection. |
Global Load Balancing |
|
VTM-45011 |
Fixed an issue where a request rule that used the TrafficScript function request.setRemoteIP() on a virtual server configured with GLB could cause the zeus.zxtm child process to restart. |
VTM-44973 |
Fixed an issue where a zeus.zxtm child process could restart if the GLB feature was used without a GeoIP database loaded. Where a GLB algorithm with geographic effect is used and no location can be discovered for a DNS query, for example if the source IP address is in a private range, the nearest datacentre calculation will no longer select the datacentre nearest to 0"N 0"E. In this situation DNS answers for any of the datacentres can be returned at random according to their weighting in response to a DNS request made to a GLB virtual server. The locations.cfg configuration file can be used to give geographic locations to private IP ranges. |
DNS Server |
|
VTM-44992 |
Fixed an issue where a virtual server using the built-in DNS server could fail to find the most specific case-insensitive match, if a wildcard was present in zone file. |
VTM-37162 |
Fixed an issue which prevented the Traffic Manager's built-in DNS server from using DNSSEC NSEC/NSEC3 with resource record types greater than 255. |
VTM-36262 |
The Traffic Manager's built-in DNS server now supports CAA records. |
SSL/TLS and Cryptography |
|
VTM-45042 |
Fixed an issue where a virtual server receiving an invalid TLS client hello could emit log messages referring to an 'IP Prefix' even when the 'ssl_trust_magic' configuration setting was disabled. |
VTM-41781 |
Fixed an issue where a virtual server with 'log!ssl_failures' enabled displayed wrong timings in the event log when a connection timed out during the TLS handshake - the "Client idle since" field now contains the time at which the connection was closed, having failed to complete the TLS handshake. |
Logging |
|
VTM-44118 |
Fixed an issue that could lead to increase in log buffer size with no limit in case of any failed communication with eventd process. |
Pulse Secure Virtual Traffic Manager Appliance
The following table lists issues that have been fixed and are resolved by upgrading to this release.
Report Number |
Description |
Appliance OS |
|
VTM-45172 |
Updated the appliance kernel to version 4.15.0-166.174, and updated packages installed on the appliance. These updates include changes addressing: CVE-2019-19449 CVE-2020-3702 CVE-2020-16592 CVE-2020-21913 |
Cloud Platforms |
|
VTM-45058 |
Fixed an issue that appliance upgrade could fail if the appliance's grub2 configuration did not match the disk device that the system booted from. |
VTM-43524 |
Fixed an issue where a software installation of the Traffic Manageron the EC2 platform could log failures regarding 'awstool', if the OS-supplied netcat program did not support Unix domain sockets. |
Pulse Secure Virtual Web Application Firewall
The following table lists issues that have been fixed and are resolved by upgrading to this release.
Report Number |
Description |
WAF-1111 |
Fixed an issue preventing the application log details page from loading. |
WAF-1112 |
Fixed an issue preventing the download of application logs. |
WAF-1113 |
Improved logging when parsing body data. |
WAF-1106, |
Reverted back to using cx_Freeze now that it supports python 3.9 for improved memory and disk space usage. |