Bug ID 485202: LDAP agent does not escape '=' character in LDAP DN

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4

Fixed In:
12.0.0, 11.6.0 HF5

Opened: Oct 17, 2014
Severity: 4-Minor

Symptoms

Starting from BIG-IP 11.6.0, session variables may have modifiers when used in configuration, such as: %{session.logon.last.ldap.dn:ldapdn} With session variable modifier "ldapdn", the resultant value should be escaped by LDAP DN rules. The rules include an equals (=) character which should be escaped, but it is not.

Impact

Depends on the purpose of usage session variable with "ldapdn" modifier in a configuration.

Conditions

LDAP session variable that contains LDAP DN is used in configuration with "ldapdn" session variable modifier.

Workaround

It is possible to escape '=' character using the Variable Assign agent before using that session variable with the modifier in other configurations.

Fix Information

Now the session variable modifier "ldapdn" escapes the equal sign (=) character as well as other characters that require escaping.

Behavior Change