Bug ID 506355: Importing an XML file without defined entity sections

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP ASM(all modules)

Known Affected Versions:
4.5.0, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.6.2 HF1, 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.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF5, 11.5.2 HF1

Opened: Feb 12, 2015

Severity: 3-Major

Symptoms

Importing an XML file without entity sections defined will not create default wildcard entities in the security policy.

Impact

Policy was not created with default entities as expected.

Conditions

Importing a partially defined XML security policy file.

Workaround

Add the missing entities after importing the incomplete XML file.

Fix Information

Previously, importing an XML file without defining the entity sections resulted in an empty URL wildcard list. Now, this process creates default wildcard entities in the security policy, as expected.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips