Bug ID 920301: Unnecessarily high number of JavaScript Obfuscator instances when device is busy

Last Modified: Dec 20, 2023

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2

Fixed In:
15.1.2, 14.1.3.1

Opened: Jun 23, 2020

Severity: 3-Major

Symptoms

When the device has high CPU or I/O rate, it can cause the JavaScript Obfuscator to run multiple times simultaneously, causing even higher CPU usage.

Impact

High CPU Usage.

Conditions

-- ASM/DoS/FPS are provisioned. -- BIG-IP device is experiencing a high CPU or I/O rate.

Workaround

None.

Fix Information

The system now avoids creating multiple JavaScript Obfuscator processes.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips