Bug ID 760878: Incorrect enforcement of explicit global parameters

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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, 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

Fixed In:
15.0.0, 14.1.0.6, 13.1.1.5, 12.1.5

Opened: Mar 10, 2019

Severity: 3-Major

Symptoms

A false positive or false negative enforcement of explicit global parameter.

Impact

Wrong blocking/violations. The parameter is not found, and the wildcard * parameter is enforced instead.

Conditions

-- A configuration with more than 255 security policies. -- Policies configured with an explicit parameter that is unique (for example, 'static', a disabled signature, etc.). -- Attempt to enforce that parameter.

Workaround

Make the explicit parameters a wildcard parameter.

Fix Information

Explicit parameters are enforced correctly on all parameters.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips