Bug ID 716746: Possible tmm restart when disabling single endpoint vector while attack is ongoing

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP AFM(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, 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, 14.1.3.1, 14.1.4, 14.1.4.1, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.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, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1

Fixed In:
16.1.0, 16.0.1.2, 15.1.3, 14.1.4.2, 13.1.0.7

Opened: Apr 24, 2018

Severity: 3-Major

Symptoms

tmm restarts.

Impact

tmm can crash and restart. Traffic disrupted while tmm restarts.

Conditions

-- AFM DoS single endpoint (sweep or flood) vector is configured. -- The attack is ongoing. -- The attack vector is being mitigated in hardware (HW). -- The vector is manually disabled.

Workaround

If you do not want to mitigate, set the mitigation_threshold to infinite. Note: Do not disable the single endpoint vectors when an attack is ongoing and the vector is being mitigated in HW.

Fix Information

tmm no longer restarts when disabling single endpoint vector while an attack is ongoing.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips