Bug ID 514246: connflow_precise_check_begin does not check for NULL

Last Modified: Dec 10, 2018

Bug Tracker

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

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5

Fixed In:
12.0.0, 11.6.0 HF6, 11.5.4

Opened: Mar 24, 2015
Severity: 3-Major
Related AskF5 Article:
K35133578

Symptoms

Currently connflow_precise_check_begin does not check for NULL for its parameters while hudproxy has plenty of places where it calls connflow_precise_check_begin with NULL.

Impact

This leads to NULL pointer dereference and subsequent tmm crash

Conditions

Connection Rate Limit is configured

Workaround

This issue has no workaround at this time.

Fix Information

Fix NULL pointer dereference in connflow_precise_check_begin

Behavior Change