Bug ID 639236: Parser doesn't accept Contact header with expires value set to 0 that is not the last attribute

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.6.1, 11.6.2, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0, 12.1.2 HF1, 11.6.3

Opened: Jan 13, 2017

Severity: 2-Critical

Related Article: K66947004

Symptoms

Incoming SIP REGISTER messages are rejected by the SIP MRF parser when they contain Contact header expires value set to 0 that is not the last attribute

Impact

REGISTER is rejected with a '400 Bad request' error message

Conditions

If the Contact header has an expires value of 0 and it's not the last attribute, for example: Contact: <sip:+414000400@10.0.0.42:5060>;expires=0;q=0.1.

Workaround

None.

Fix Information

Updated SIP parser to handle a Contact header with an expires value set to 0 that is not the last attribute.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips