Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP AFM
Known Affected Versions:
11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.1.0, 12.0.0 HF3
Opened: Oct 06, 2015 Severity: 3-Major
When an AFM rule is configured to "unknown" geographic location, the rule stops functioning when another entity (geolocation or IP address) is added to the same list of addresses in the rule.
Confusing, inconsistent, and apparently broken behavior.
Configure an address list of AFM rule with "unknown" source Geo-entity and at least one other entity (geolocation or IP address).
Do not configure "unknown" geographic locations as one of the entities in an address list. Known geographic locations work correctly.
The code logic is fixed to properly handle the "unknown" geolocation. Now the user can configure "unknown" geolocation as one of the entity in an address list.