Bug ID 1980601: Number of associated signatures for a signature-set appears zero

Last Modified: Jul 14, 2025

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

Known Affected Versions:
17.1.2.1, 17.1.2.2

Opened: Jul 10, 2025

Severity: 5-Cosmetic

Symptoms

Number of associated signatures for a signature-set appears zero in REST API and GUI. /mgmt/tm/asm/signature-sets/{UUID} returns 'signatureCount' of which value is incorrectly shown zero. Signature set screen in the GUI shows list of signature-sets with number of signatures of each sets. This number is incorrectly displayed zero. Security ›› Options : Application Security : Attack Signatures This is a cosmetic issue. Signature enforcement is performed for the affected signature-set even though the number is reported as zero. By selecting an affected signature-set in the GUI, you can see the associated signatures.

Impact

Number of signatures is reported as zero for an affected signature-set

Conditions

Via REST API you sent PATCH request to the endpoint /mgmt/tm/asm/signature-sets/{UUID} The JSON body is badly structured or you sent the same PATCH request twice.

Workaround

Update the endpoint with correctly structured JSON, and change one of the attribute value.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips