Last Modified: Jul 12, 2023
Known Affected Versions:
14.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 14.1.2, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 15.0.0, 15.0.1, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 15.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
16.0.0, 15.1.1, 220.127.116.11
Opened: Jan 12, 2020 Severity: 2-Critical
When using an iRule to disable bot profile, and causing it to be disabled (for the entire connection) during a CAPTCHA challenge -- TMM will crash.
Traffic disrupted while tmm restarts.
-- Bot Defense profile is attached to the Virtual Server, with a CAPTCHA mitigation. -- An iRule is attached to the virtual server, which disables bot profile. -- Sending a request that is responded with a CAPTCHA, then sending (in the same connection), a request that disable the bot profile, and then answering the CAPTCHA.
When using an iRule to disable bot defense profile on certain conditions, add an "else" clause for re-enabling the profile, taking note that all ::disable iRule commands are effective for the entire connection, and not just the transaction.
TMM no longer crashes when disabling bot defense profile for the entire connection.