Last Modified: May 29, 2024
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3
Fixed In:
17.1.1, 16.1.4, 15.1.10
Opened: Mar 30, 2023 Severity: 2-Critical
Calling the HTTP::disable command more than once in an irule can result in the tmm process crashing.
BIG-IP may crash during an HTTP CONNECT request from a client.
->Basic http configuration -> iRule when CLIENT_ACCEPTED { set collects 0 TCP::collect } when CLIENT_DATA { if { $collects eq 1 } { HTTP::disable HTTP::disable } TCP::release TCP::collect incr collects } when HTTP_REQUEST { log local0. "Request" } when HTTP_DISABLED { log local0. "Disabled" }
Avoid calling HTTP::disable more than once per connflow
Treat disable via iRule as a NOP when a disable is in progress