Bug ID 507575: An incorrectly formated NAPTR creation via iControl can cause an error.

Last Modified: Apr 28, 2025

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

Known Affected Versions:
11.4.1, 11.5.3, 11.5.3 HF1, 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.3 HF2, 11.4.1 HF9

Opened: Feb 17, 2015

Severity: 3-Major

Symptoms

NAPTR records are somewhat complicated and if an incorrect set of string arguments are passed to iControl, the string parsing can fail and generate unhelpful error messages.

Impact

Potential failure of iControl parsing.

Conditions

Specifically, it is valid to have empty strings as some of the fields of a NAPTR record. However, these empty strings must be quoted as empty strings. An example of a valid empty string parameter foo.example.com. 19799 IN NAPTR 100 7 "u" "good" "" bar.example.com. Not quoting the empty parameter (after "good") confuses the parser into thinking that not enough parameters were passed. This causes a segfault and the error.

Workaround

Use quotes around empty strings such as: foo.example.com. 19799 IN NAPTR 100 7 "u" "good" "" bar.example.com.

Fix Information

The string parser has been made tolerant of missing parameters for these records and will now report an error.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips