Last Modified: May 29, 2024
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3
Fixed In:
15.0.0, 14.1.3.1, 13.1.3.4, 12.1.5
Opened: Feb 25, 2019 Severity: 3-Major
When a request is sent to the virtual server which meets the conditions specified, TMM may crash.
Traffic disrupted while tmm restarts.
When all of the following conditions are met: -- Virtual server configured with iRule that contains HTTP::respond or HTTP::redirect in an LB_FAILED event. -- A command in an LB_FAILED event (does not have to be in the same iRule as the previous point, but must be attached to the same virtual server), that parks the iRule (e.g., table, session, persist, after, HSL). -- A CLIENT_CLOSED event is present. -- The pool member fails in some manner, triggering LB_FAILED
Add reject command to LB_FAILED event to force the serverside of the connection closed before response is sent to the client.
None