Bug ID 695878: Signature enforcement issue on specific requests

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.5, 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.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 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, 13.1.1.5, 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.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

Fixed In:
15.0.0, 14.1.2.1, 14.0.1.1, 13.1.3, 12.1.5, 11.5.6

Opened: Nov 22, 2017

Severity: 4-Minor

Symptoms

Request payload does not get enforced by attack signatures on a certain policy configuration with specific traffic.

Impact

Attack signatures are not enforced on the payload of this request at all.

Conditions

-- The violation 'Request exceeds max buffer size' is turned off. -- The request is longer than the max buffer size (i.e., a request is larger than the internal long_request_buffer_size).

Workaround

Turn on the violation in blocking 'Request exceed max buffer size'.

Fix Information

The operation now looks into part of the payload for the attack signatures enforcement.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips