Bug ID 420376: ASM crashed during ASM encoding configuration

Last Modified: Feb 13, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(all modules)

Known Affected Versions:
10.2.4, 11.2.0, 11.2.1, 11.3.0, 11.4.0

Fixed In:
11.5.0, 11.4.0 HF3, 11.3.0 HF6, 11.2.1 HF8

Opened: May 02, 2013
Severity: 3-Major
Related AskF5 Article:
K66115925

Symptoms

When a security policy has an encoding that has many secondary encodings (such as the Chinese encoding), and it receives transactions with parameters or URLs in different secondaries encoding at some high rate, if at the same the user reconfigures the security policy and changes the encoding to one of the secondary encodings, there is a chance that the Enforcer internal encoding table will get corrupted.

Impact

BD core when customer trying to apply policy on active unit.

Conditions

BD core when customer trying to apply policy on active unit.

Workaround

This issue has no workaround at this time.

Fix Information

The Enforcer internal encoding table is no longer corrupted when all of these conditions are met: - A security policy has an encoding language that has many secondary encoding languages (such as the Chinese encoding). - The Enforcer receives transactions at a high rate with parameters or URLs in different secondary encoding languages. - At the same time the user reconfigures the security policy and changes the encoding to one of the secondary encoding languages.

Behavior Change