Bug ID 596631: SIP MRF: Wrong listener may be deleted during media deny-listener deletions, causing crash later

Last Modified: Oct 06, 2020

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2

Fixed In:
13.0.0, 12.1.2

Opened: Jun 01, 2016
Severity: 2-Critical

Symptoms

A SIP media flow deny-listener was to have been deleted but an unrelated listener was deleted instead due to an incorrect address/port match. For example, when the wrongly deleted listener is later meant to be deleted, there might be a SIGFPE with assertion failure "Assertion "bound listener" failed.".

Impact

Later when the wrongly deleted listener is referenced, the TMM crashes.

Conditions

A SIP MRF media flow existed and was deleted. An unrelated flow exists with an address/port with wildcards such that it includes that of the media flow.

Workaround

None

Fix Information

When a SIP media flow deny-listener is searched for deletion, an exact match is required that uniquely identifies the deny-listener, so that an unrelated listener is not deleted.

Behavior Change