Last Modified: Jul 12, 2023
Affected Product(s):
BIG-IP ASM
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.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
Fixed In:
15.1.0, 14.1.4.2, 13.1.4.1
Opened: Jun 11, 2019 Severity: 3-Major
ASM challenge makes Google Analytics stats appear as if they are 'Direct' instead of 'Organic'.
Incorrect data is displayed in the Google Analytics dashboard.
Scenario 1: -- ASM provisioned. -- ASM policy attached to a virtual server with challenge mitigation enabled (as part of brute force protection, for example). Scenario 2: -- Bot defense profile attached to a virtual server with challenge mitigation enabled. Scenario 3: -- DoS Application profile attached to a virtual server with challenge mitigation enabled.
Have an iRule that injects google-analytics.js into the challenge white page at the HTTP_RESPONSE_SENT time event.
ASM now handles the backend's response to fix up document.referrer for tools that read this property.