Loading...
Loading...
This issue has been observed with bot-defense signatures, resulting in log lines that appear as follows: Notice MCP message handling failed in 0xacdf00 (16973843): Jun 24 19:34:45 on 1 - MCP Message: notice create { notice bot_defense_compiled_signatures { notice bot_defense_compiled_signatures_parent_profile "/Common/a_profile_name" notice bot_defense_compiled_signatures_name "/Common/a_signature_name" ... The 16973843 error number is a fingerprint for this.\
Config settings aren't honored by tmm. In the case of signatures, this can result in traffic that should be blocked but is not
This typically requires thousands of the same config objects (e.g., bot-defense signatures), but it can rarely happen with many fewer
The root cause is that DOS L7 config object names are hashed into a 32-bit number. This can cause collisions, which lead to the bug. So changing names can prevent the collisions, e.g., by appending a random number to the name But note that this is a probabilistic fix and is not guaranteed to work with the first random number
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.