Bug ID 1750837: Sig_cve field is not populated in remote logs

Last Modified: Mar 25, 2025

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

Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1

Fixed In:
17.5.0

Opened: Nov 18, 2024

Severity: 3-Major

Symptoms

When sig_cve field is selected in remote logging profile, and a valid signature violation is reported, sig_cve data is not populated while sending logs to remote syslog.

Impact

Missing sig_cve data in remote logs.

Conditions

1) A remote logging profile is configured. 2) sig_cve field is selected in the remote logging profile 3) Signature violation is reported whose sig_cve data is available.

Workaround

None

Fix Information

Changes were made to how BD stores information about which fields have been configured in remote logger. BD now correctly identifies that sig_cve field is configured and sends data accordingly.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips