Last Modified: Jul 07, 2025
Affected Product(s):
BIG-IP ASM
Known Affected Versions:
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, 17.1.2.2, 17.5.0
Fixed In:
17.5.1
Opened: Mar 19, 2025 Severity: 2-Critical
* XML/JSON traffic gets flagged or blocked with a Malformed XML data or Malformed JSON data violation despite the URL having a content-profile associated with it. * When the violation gets raised, the violation details lists the profile as "N/A". * The XML/JSON content profiles are visible when viewing the content profile configuration via WebUI. However, corresponding database tables lose integrity, which results false positive.
XML/JSON traffic gets flagged or, if enforced, blocked despite the content profile associated to the URL.
Any change followed by 'Apply Policy' on a policy can ruin the integrity of corresponding database that might affect other policies, and false positive would start after subsequent 'Apply Policy' or global configuration update.
Make a spurious policy change to the affected XML or JSON profile (e.g., updating its Description), followed by applying policy changes via 'Apply Policy,' This helps resolve the issue by populating a new entry in the database table for this policy. Avoid making any change on any GraphQL profile to prevent it from re-occurring.
Configuration change will not ruin the integrity of the database tables.