Related Articles

KB44238 - vTM GUI becomes inaccessible after upgrading to 18.3 or above

SA43667 - 2018-03 Out-of-Cycle Advisory: SAML allow authentication bypass via incorrect XML canonicalization

4656 - Attempting to upgrade the vTM-VA failed with the message "The upgrade process has encountered an error and cannot continue. Please contact your support provider to help you fix this problem."

SA44101 - 2019-04: Out-of-Cycle Advisory: Multiple vulnerabilities resolved in Pulse Connect Secure / Pulse Policy Secure 9.0RX

SA43681 - 2016-11: CSRF vulnerability with Brocade Virtual Traffic Manager (vTM) (CVE-2016-8201)

KB44282 - Host checker fails to launch if the windows login id contains Non-English character post upgrading the PCS device

SA44503 - 2020-06: Out-of-Cycle Advisory: Pulse Secure Client TOCTOU Privilege Escalation Vulnerability (CVE-2020-13162)

SA43582 - Out-of-Cycle Advisory: Virtual Traffic Manager (vTM) Password Management Vulnerability/Sensitive Data Protection Vulnerability/Principle Of Least Privilege Violation

KB43699 - ZCLI output "HTML Error: Failed to load page" occurs intermittently when running concurrent SOAP scripts

KB44167 - Unable to launch Client components when proxy is configured on browser post upgrading to 9.0R4

< Back to search results

Article

KB44049 - "SSL Connection Error - Invalid key exchange message" post upgrading the vTM to 18.3

« Go Back

Information

Last Modified Date	9/6/2019 6:10 PM

Synopsis

This article describes an issue encountered by a user when accessing the resource through virtual traffic manager.

Problem or Goal

After upgrading vTM to 18.3, end users are not able to connect to some internal websites and would see an error message stating

SSL Connection Error - Invalid key exchange message

vTM logs would show the message:

An error occurred: Failed to connect to server: Invalid key exchange message

Cause

This issue is caused by a bug in the vTM (VTM-40373), which by default includes PSS based signatures in its Client Hello even though it doesn't support them.

Solution

To resolve this issue, upgrade the Traffic Manager to 18.3R1 or later.

Related Links

Attachment 1

Created By	Rajkumar Tamilarasan