REGEXVAULTv2.0
Security/Injection Patterns
Verified Safe

LDAP Injection Pattern Regex for Java

/[)(|*\\\x00]|(?:objectclass|objectCategory|objectGUID|samAccountName|userPrincipalName|memberOf)\s*=|(?:\(uid=)|(?:cn=)(?:[^,)]*\*)/i

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching ldap injection pattern, ported and verified for Java. In security-sensitive code, using an unverified regex can open the door to both false positives and denial-of-service attacks. The snippet below is ready to drop into your Java project — whether you're validating in a Spring Boot controller, a Jakarta EE service, or a standalone utility class.

Java Implementation

Java
// LDAP Injection Pattern
// ReDoS-safe | RegexVault — Security > Injection Patterns

import java.util.regex.Pattern;

public class LdapInjectionPatternValidator {
    private static final Pattern PATTERN =
        Pattern.compile("[)(|*\\\\\\x00]|(?:objectclass|objectCategory|objectGUID|samAccountName|userPrincipalName|memberOf)\\s*=|(?:\\(uid=)|(?:cn=)(?:[^,)]*\\*)");

    public static boolean validate(String input) {
        return PATTERN.matcher(input).matches();
    }

    // Example
    public static void main(String[] args) {
        System.out.println(validate("*)(uid=*))(|(uid=*")); // true
    }
}

Test Cases

Matches (Valid)
Rejects (Invalid)
*)(uid=*))(|(uid=*normal.user@example.com
admin)(objectClass=*John Smith
)(cn=*)CN=Users,DC=example,DC=com

When to use this pattern

This pattern is drawn from the Security > Injection Patterns category and carries a ReDoS-safe certification. That matters for Java developers because critical in Java applications since the JVM regex engine uses backtracking and is susceptible to ReDoS without careful pattern design. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

LDAP injection is common in authentication systems where usernames/emails are used to build LDAP search filters. The wildcard * is the most impactful character — allows blind enumeration of all directory entries.

Technical Notes

LDAP special characters: ( ) * \ and null byte. Classic injection: *(|(mail=*)) returns all records when injected into a filter. Defense: use LDAP parameter encoding to escape special characters in search filters. RFC 4515 defines the escape sequences.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern