Bug ID 752047: iRule running reject in CLASSIFICATION_DETECTED event can cause core

Last Modified: Sep 06, 2019

Bug Tracker

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

Known Affected Versions:
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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 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.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5

Fixed In:
15.0.0, 14.1.0.6, 13.1.1.5

Opened: Dec 05, 2018
Severity: 2-Critical

Symptoms

The CLASSIFICATION_DETECTED iRule event can run very early when classification happens in the classification database (srdb). If the iRule then issues a reject command, tmm cores.

Impact

tmm restarts. Traffic disrupted while tmm restarts.

Conditions

CLASSIFICATION_DETECTED on L4 executing reject command.

Workaround

None.

Fix Information

iRule running reject in CLASSIFICATION_DETECTED event no longer causes tmm core.

Behavior Change