Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Fixed In:
13.1.0
Opened: Mar 17, 2017 Severity: 4-Minor
The issue occurs when user specifies a URL in an LTM Policy where the path contains the hash (#) character. This character was not considered to be valid, and so the valid-character checking logic treats the URL as invalid.
User is unable to specify a URL containing the hash (#) character.
User specifies a URL, say for forwarding a redirect, that contains a hash (#) character. For example, defining a policy to redirect user connections to a URL like: http://www.example.com/path1/path2/#/otherpath
In some instances, it may be possible to substitute the hash character (#) with its URL-encoded equivalent (%23).
URLs used in LTM Policies correctly treat the hash character (#) as an allowed character.