Bug ID 1030185: TMM may crash when looking up a persistence record using "persist lookup" iRule commands

Last Modified: Sep 23, 2021

Bug Tracker

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

Known Affected Versions:
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, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 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, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2

Opened: Jun 30, 2021
Severity: 2-Critical

Symptoms

Tmm may crash with a SIGSEGV when looking up a persistence record in an iRule when using the "any" flag

Impact

Traffic disrupted while tmm restarts.

Conditions

-- The persistence entry exists on a virtual server other than the virtual server the iRule is configured on. -- The iRule contains [persist lookup source_addr "[IP::client_addr] any"]

Workaround

Discontinue the use of the "any" flag in the persist lookup iRule.

Fix Information

None

Behavior Change