LoadMaster 126.96.36.199 Release Notes (GA)
LMOS Version 188.8.131.52 is a security update for the LMOS General Availability (GA) branch, made available on 25 April 2022. Please read the sections below before installing or upgrading to this release.
Supported Models for Upgrade
Existing Known Issues
Before You Upgrade (READ ME FIRST)
Please pay special attention to the issues below before you begin an upgrade to this LMOS release.
Generation of 4096-bit DHE Key
During an upgrade to this version of LMOS from a version prior to 184.108.40.206, a new 4096-bit DHE key is generated. On smaller LoadMasters, this can lead to significant CPU and memory consumption that could impact regular virtual service traffic. So, Kemp strongly recommends that this update be performed in a maintenance interval.
Best Practices Cipher Set
In LMOS 220.127.116.11, the BestPractices cipher set was updated. If you are upgrading from a version prior to 18.104.22.168, this change is effective immediately after upgrade to this release. This change was made to improve LoadMaster security and conform to the latest industry best practices.
If you depend on any of the cipher sets being removed from the BestPractices set, then before you upgrade you must create a custom cipher set that contains these ciphers and assign this new custom cipher set to the Virtual Services that are currently using the BestPractices cipher set. After this is done, you can upgrade to this release and your services will continue to use the old ciphers. If you do not, then after upgrade any clients that depend on these ciphers being available will no longer be able to connect.
It is recommended, however, that you migrate your services as soon as possible to use the new BestPractices cipher set. For more information on the cipher suites removed from the set, please see the LMOS 22.214.171.124 Release Notes.
Supported Models for Upgrade
This release of LMOS is supported on the Hardware and Virtual models shown in the first three columns of the table below. It is not supported and should not be installed on any model listed in the two columns at right. This update patch can be applied to any supported model regardless of licensing (e.g., SPLA, MELA) or platform (e.g., hardware, local cloud, public cloud).
|Supported Bare Metal Models||UNSUPPORTED
If your model number is not listed above, please see the list of End of Life models.
You can upgrade to this release of LMOS from any previous 7.2.x release. For full upgrade path information, please see the article Kemp LoadMaster Firmware Upgrade Path.
Upgrade Patch XML File Verification Notes
By default, verification of the digital signature on upgrade images is required in LMOS 126.96.36.199 and above. See the Update Verification Options setting under System Administration > Miscellaneous Options > WUI Settings. If the unit you are upgrading is set to require validation, you'll need to supply the XML Verification File supplied with this release.
- In previous releases, two verification files were provided: one for pre-7.2.51 systems and one for later systems. This restriction has been removed with the 188.8.131.52 release; if upgrading from firmware 184.108.40.206 / 220.127.116.11 and above you can use the XML file provided with this release. If upgrading from any other firmware version you must following the upgrade path detailed in Kemp LoadMaster Firmware Upgrade Path article.
- LoadMasters running an LMOS version prior to 7.2.49 do not provide the option of XML file verification in the UI or API. If you are upgrading from one of these releases to this release, you can verify the digital signatures offline using a manual process documented on the support website.
This patch updates LoadMaster's default OpenSSL libraries to Version 1.1.1n to address the OpenSSL security vulnerability described in CVE-2022-0778. In summary, this exploit leverages an internal OpenSSL bug that can cause an infinite loop to occur when parsing certificates. As a result, parsing a client certificate with an elliptic curve public certificate (or a public certificate with explicit elliptic curve parameters) may trigger the infinite loop and thus a denial of service attack. Further details are in the vulnerability database entry at the link above.
Note that this patch does not update the earlier version of OpenSSL present on LoadMaster (Version 1.0.2) to address CVE-2022-0778. This earlier OpenSSL version is used on LoadMaster only when the Certificates & Security >SSL Options > OpenSSL Version parameter is set to Use older version. If this is set to Use current version (the default value), then OpenSSL 1.1.1 is used.
Fortunately, with OpenSSL 1.0.2, there is no vulnerability to this exploit during the SSL handshake because of the handshake design in OpenSSL 1.0.2. On LoadMaster, the vulnerability can only be exploited by an administrative LoadMaster user who installs a specially crafted certificate and public key, and therefore presents a much lower risk of exposure to this vulnerability. This issue will be addressed in a future release.
Existing Known Issues
Network Telemetry: The 18.104.22.168 version of the Network Telemetry Add-on may not function after being enabled on one or more interfaces. Flow data will not be sent to the Flowmon Collector and the following message will appear repeatedly in the system log:
flowd: Monitor for interface 0 (pid xxxxx) died - exited with status 1
The workaround is to remove the 22.214.171.124 version of the add-on package and install the 126.96.36.199 version, using the controls on the System Configuration > System Administration > Update Firmware page. The add-on package can be downloaded from this web page.
|PD-19953||SNMPv2c Walk: When using SNMP Version 2c, the Walk command may not work, returning no data. The workaround is to enable the SNMPv3 check box in the SNMP configuration and then disable it. The Walk command should then work properly via SNMPv2c.|
|PD-19704||GEO Cluster Status: When adding a Cluster that is unavailable (DOWN) to a Site, the Site may reflect the Cluster's status as available (UP) for a short time before changing to DOWN.|
GEO: Modifying an FQDN entry displays a spurious error on the system console, similar to the one shown below. The FQDN is modified properly.
|PD-19093||GEO: Cannot configure GEO into partnering mode unless there is at least one FQDN already defined.|
|PD-18646||Certificate-Based Administrative Login: Using a certificate that does not have a SAN attribute (i.e., no Principal Name) results in a failed login attempt.|
|PD-18615||GEO: No statistics (queries per second, etc.) are displayed for a site if the FQDN is configured to use the "All Available" Selection Criteria.|
|PD-18099||Client Certificates: Authentication may be denied if multiple "Other names" are present in the client certificate.|
|PD-17927||LDAP UI Access: Under certain circumstances, a user that has no LDAP credentials can gain access to the UI.
|PD-15872||LDAP/Syslog: StartTLS is not working when the Server Certificate Validation flag is enabled.|
|PD-15633||GEO: If you add a Zone Name to GEO after you have created working FQDNs, GEO may no longer respond to queries for one or more of the FQDNs after the Zone Name is added. The workaround is to remove and then re-add the FQDNs that are no longer working.|
|PD-15475||VS Redirects: If you attempt to upload a new redirect error HTML file to a Virtual Service with Not Available Redirection Handling enabled while traffic is currently being redirected, then traffic to the VS is dropped. Click the Error Message radio button in the UI and the VS begins accepting connections again.|
|PD-15354||SSO Timeout: In LMOS 188.8.131.52, a fix was introduced for issues that caused an SSO client to not be properly logged out when the configured session timeout expires. It has been observed that while sessions do timeout, they are not always closed immediately upon the expiry of the timer; it can take close to a minute longer for the session to be closed.|
|PD-15294||ESP Verify Bearer Header: LoadMaster does not return an error when an encrypted token is received and there is no SSL certificate assigned to the VS to decrypt the token.|
|PD-15172||ESP Verify Bearer Header: Validation is not working when "Allowed Virtual Hosts" and "Allowed Virtual Directories" are blank on the Virtual Service.|
|PD-14943||Single Sign On: When Form Based Authentication is enabled on the server side, it is possible that after filling out correct credentials and submitting the login form, the form will be presented again; once the second login form is submitted with correct credentials, the login succeeds.|
|PD-13899||ACLs and Real Servers: Real Servers located on networks on which LoadMaster also has an IP address are always allowed to access Virtual Services on that network interface regardless of any access control list (ACL) settings on LoadMaster. For Layer 7 services, this issue can be worked around using Content Rules. The workaround for other services is to block access for local Real Servers (if desired) on another network device (firewall, switch, router, etc.).|
|PD-12838||ESP / SSO: The ESP Permitted Group SID(s) setting is not working as expected when configured on a SubVS.|
|PD-12616||WAF / Compression: With Web Application Firewall (WAF) enabled, compressed files are incorrectly decompressed. As a workaround, ensure compression is enabled in VS Advanced Properties by selecting the Enable Compression option.|
|PD-12492||Downgrade: If an Azure VLM is downgraded to the LTS firmware release (7.1.35.x), the WUI may display in the top right-hand corner that the VLM is a Hyper-V VLM. This indicates that the Azure VLM Add-On Package must be added to the system to provide full Azure VLM functionality. If this occurs, please contact Kemp Support to get the required add-on package.|
|Hardware Support: The LoadMaster models LM-X15, LM-X25, and LM-X40 do not support the following SFP+ modules: LM-SFP-SX (SFP+ SX Transceiver 1000BASE-SX 850nm, 550m over MMF), LM-SFP-LX (SFP+ LX Transceiver 1000BASE-LX 1310nm, 10KM over SMF).|
HA / NTP: Configuring NTP for the first time after the system is running in High Availability (HA) mode and when the current time on the two machines is not correct, may cause the systems to both go into the Active state. The workaround for the issue of having two Active LoadMasters in HA is as follows:
|PD-12147||ESP / RADIUS: In a LoadMaster configuration with ESP and Radius server-side authentication enabled, sessions may fail to be established.|
|PD-12058||Browser Support: An issue exists when connecting to the LoadMaster WUI when using newer versions of the Firefox browser on initial configuration of a hardware FIPS LoadMaster.|
|PD-11861||RADIUS / IPv6: IPv6 is not supported by the current RADIUS implementation in the LoadMaster for both WUI Authorization and ESP Authentication.|
|PD-11166||Networking: Azure LoadMasters are not translating the additional network address between the Master and Slave correctly.|
|PD-11044||SharePoint Virtual Services: A second authentication prompt is presented when a file is uploaded to SharePoint with the following configuration: WAF is configured with Process Responses enabled on the main Virtual Service and KCD is enabled on the SubVS level for server-side authentication.|
|PD-10917||HA: An issue exists when setting up a 2-armed HA Virtual LoadMaster in Azure.|
|PD-10784||HA: Configuring LoadMaster HA using eth1 on an Amazon Web Services (AWS) Virtual LoadMaster does not work.|
|PD-10490||WAF: The vsremovewafrule RESTful API command does not allow multiple rules to be removed. This problem has been fixed.|
|PD-10193||Exchange 2010 Virtual Services: A WAF, ESP, and KCD configuration with Microsoft Exchange 2010 is not supported.|
|PD-10188||Browser Support: (Safari) When adding a Real Server to a Virtual Service or SubVS using the Safari browser, the list of available Real Servers is not available.|
|PD-10159||Statistics: When upgrading firmware from version 7.1.35.n, CPU and network usage graphs are not appearing. As a workaround, reset the statistics in the WUI.|
|PD-10136||Clustering: In a LoadMaster cluster configuration, a new node can be added with the same IP address as an existing node.|
|WAF: There is an API command to list individual rules in a ruleset, but there is no command to list the available rulesets themselves.|
|PD-9765||GEO: DNS TCP requests from unknown sources are not supported.|
|PD-9507||Networking: Unable to add an SDN controller using the RESTful API/WUI in a specific scenario.|
|PD-9375||SharePoint Virtual Services: Microsoft Office files in SharePoint do not work in Firefox and Chrome when using SAML authentication.|