Bug ID 928685: ASM Brute Force mitigation not triggered as expected

Last Modified: Feb 07, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(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.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 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.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.4.1

Opened: Jul 20, 2020
Severity: 3-Major
Related Article:
K49549213

Symptoms

Under certain conditions the Brute Force mitigation will not be triggered.

Impact

Brute Force mitigation is not triggered as expected.

Conditions

- ASM enabled - Brute Force mitigation enabled

Workaround

The following iRule will look for an issue with the authorization header and will raise an custom violation when this is happening: when ASM_REQUEST_DONE? {     if { [catch { HTTP::username } ] } {?      log local0. "ERROR: bad username";?      ASM::raise bad_auth_header_custom_violation ?    } }

Fix Information

Brute Force mitigation is now triggered as expected.

Behavior Change