Bug ID 431283: iRule binary scan may core TMM when the offset is large

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.3.0, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF6, 11.5.3 HF2

Opened: Sep 20, 2013

Severity: 2-Critical

Related Article: K15138

Symptoms

Binary command does not check if the offset argument is beyond the internal buffer boundary, this may core TMM. Here is an example: binary scan [TCP::payload] @${offset_num}c var1 if "offset_num" is larger than payload buffer length, TMM may core.

Impact

Traffic disrupted while tmm restarts.

Conditions

Here is an example: binary scan [TCP::payload] @${offset_num}c var1 if "offset_num" is larger than payload buffer length, TMM may core.

Workaround

Check payload length and compare with the offset argument before using the command.

Fix Information

Check the offset value before moving the cursor.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips