LDAP Injection |
Attack Pattern ID: 136 (Standard Attack Pattern Completeness: Stub) | Typical Severity: High | Status: Draft |
Summary
An attacker manipulates or crafts an LDAP query for the purpose of undermining the security of the target. Some applications use user input to create LDAP queries that are processed by an LDAP server. For example, a user might provide their username during authentication and the username might be inserted in an LDAP query during the authentication process. An attacker could use this input to inject additional commands into an LDAP query that could disclose sensitive information. For example, entering a * in the aforementioned query might return information about all users on the system. This attack is very similar to an SQL injection attack in that it manipulates a query to gather additional information or coerce a particular return value.
The target application must accept a string as user input, fail to sanitize characters that have a special meaning in LDAP queries in the user input, and insert the user-supplied string in an LDAP query which is then processed.
No special resources are required beyond the ability to provide string input to the target.
Nature | Type | ID | Name | Description | View(s) this relationship pertains to![]() |
---|---|---|---|---|---|
ChildOf | ![]() | 152 | Injection (Injecting Control Plane content through the Data Plane) | Mechanism of Attack (primary)1000 | |
ChildOf | ![]() | 362 | WASC Threat Classification 2.0 - WASC-29 - LDAP Injection | WASC Threat Classification 2.0333 |