How to fix: LDAP injection indicators
LDAP filter strings may be constructed from user input without proper escaping.
Why it matters
LDAP injection allows an attacker to modify the LDAP filter logic, bypassing authentication (e.g., making any password valid), enumerating directory contents, and accessing attributes of arbitrary users in the directory.
LDAP filter special characters (* \ ( ) NUL) must be escaped before including user input in filters.
How to fix it
- 1Escape all LDAP filter special characters from user input
- 2Use an LDAP library with built-in parameterization
- 3Validate user input format before using in any LDAP operation
Code examples
Escape LDAP filter special characters
function escapeLdap(str: string): string {
return str
.replace(/\\/g, "\\5c")
.replace(/\*/g, "\\2a")
.replace(/\(/g, "\\28")
.replace(/\)/g, "\\29")
.replace(/\0/g, "\\00");
}
const filter = `(uid=${escapeLdap(userInput)})`;
// Always escape user input before including in LDAP filtersReferences
Detected automatically by VulnRadar. The check id is ldap-injection-indicators, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is LDAP injection indicators?
- VulnRadar rates this high severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id ldap-injection-indicators, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does LDAP injection indicators map to?
- It maps to CWE-90. In the OWASP Top 10 it falls under A03:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.