Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP All
Known Affected Versions:
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, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 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, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6
Opened: Jan 09, 2019 Severity: 2-Critical
iControl REST API adds unnecessary escaping to URL if it contains a wildcard character.
iControl REST API adds unnecessary escape character (\) to URL. The resulting configuration may not be interpreted correctly by the data plane because the request URL does not match with the configuration. -- One specific example: # restcurl -u admin:<password> -d '{"name":"/vdesk/test*","type":"wildcard"}' "https://host.mgmt.siterequest.com/mgmt/tm/security/anti-fraud/profile/fps_logonpage_wildcard/urls" -- Results in this: urls { /vdesk/test\\* { priority 2 type wildcard } } -- Instead of the expected: urls { /vdesk/test* { priority 2 type wildcard } }
-- Creating configuration using iControl REST API. -- Configuration includes a URL containing wildcard character.
Use TMSH to add the configuration.
None