Bug ID 1251013: Allow non-RFC compliant URI characters

Last Modified: Jul 24, 2024

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

Known Affected Versions:
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, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3

Fixed In:
17.1.1, 16.1.5, 15.1.10

Opened: Feb 22, 2023

Severity: 4-Minor

Symptoms

The MRF Parser fails if the URIs are not as per RFC. It is required to not validate against the RFC for proper URI formatting, required message headers, and usage of defined method names.

Impact

MRF parser allows URI formats which are not comply with RFC.

Conditions

- SIP URIs are not formatted as per RFC.

Workaround

None

Fix Information

Set allow-unknown-methods to enabled in SIP session profile, which relaxes the SIP parser to allow unknown SIP messages to be used.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips