Symptoms

When selenium client webdriver is detected running the Chrome browser it is not being blocked due to low score being assigned by PBD (Suspicious Browsers) mechanism.

Impact

A bot which running selenium Chrome webdriver isn't mitigated by DoSL7 PBD mechanism.

Conditions

This occurs when ASM is provisioned with proactive bot defense enabled.

Workaround

N/A

Fix Information

Only for Desktop Google Chrome browsers, the PBD javascript code checks if a plugin called "Widevine Content Decryption Module" doesn't exists, the browser considered as running via the selenium tool and will be blocked by PBD.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips