Bug ID 667922: Alternative unicode encoding in JSON objects not being parsed correctly

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.1.2, 12.1.3, 12.1.3.1

Fixed In:
12.1.3.2

Opened: Jun 05, 2017

Severity: 3-Major

Related Article: K44692860

Symptoms

JSON content might be blocked when unicode encoding is used in one of the JSON nodes.

Impact

False positive blocked request.

Conditions

Configured ASM Policy with JSON profile.

Workaround

Disable metachars checks in JSON profile.

Fix Information

The JSON parser now handles unicode sequences correctly.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips