Rule Definition
An attacker could include input that changes the LDAP query which allows unintended commands or code to be executed, allows sensitive data to be read or modified or causes other unintended behavior.

Remediation
Input validation. Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a white-list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."

Violation Code Sample

context = new InitialDirContext(env);
String searchFilter = "StreetAddress=" + address;
NamingEnumeration answer = context.search(searchBase, searchFilter, searchCtls);

Fixed Code Sample

context = new InitialDirContext(env);
//The code below constructs an LDAP query using user input address data:
String searchFilter = "StreetAddress=" + address;
// Include validate code for searchFilter
NamingEnumeration answer = context.search(searchBase, searchFilter, searchCtls);

CWE-90: Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') https://cwe.mitre.org/data/definitions/90.html Open Web Application Security Project (OWASP) https://www.owasp.org/index.php/Top_10-2017_A1-Injection