Bug ID 547732: TMM may core on using SSL::disable on an already established serverside connection

Last Modified: May 14, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.4.1, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0, 11.6.1, 11.5.4 HF2, 11.4.1 HF10

Opened: Sep 23, 2015
Severity: 3-Major

Symptoms

TMM process may crash if the SSL::disable iRule command is used on a serverside with a connection that has already established SSL.

Impact

Traffic disrupted while tmm restarts.

Conditions

Use of the 'SSL::disable serverside' iRule command on a serverside connection that has already established SSL

Workaround

Do not use SSL::disable on an event where the serverside SSL connection is already established.

Fix Information

TMM no longer cores on using SSL::disable on an already established serverside connection, it will now log a warning Connection error: hud_ssl_handler:605: disable profile (80)

Behavior Change