Bug ID 957905: SIP Requests / Responses over TCP without content_length header are not aborted by BIG-IP.

Last Modified: May 29, 2024

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

Known Affected Versions:
13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1

Fixed In:
17.0.0, 16.1.2.2, 15.1.5.1, 14.1.4.6, 13.1.5

Opened: Oct 21, 2020

Severity: 3-Major

Symptoms

SIP Requests that don't contain a content_length header are accepted and forwarded by the BIG-IP to the server. SIP Responses that don't contain a content_length header are accepted and forwarded to the client. The sipmsg parser does not treats the content_length header as a required header as part of the SIP Request / Response.

Impact

RFC 6731 non compliance.

Conditions

SIP request / response without content_length header.

Workaround

N/A

Fix Information

BIG-IP now aborts the connection of any TCP SIP request / response that does not contain a content_length header. content_length header is treated as optional for UDP and SCTP.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips