CAPEC-136: LDAP Injection
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.
Last updated
Overview
CAPEC-136 (LDAP Injection) is a standard-level attack pattern catalogued by MITRE in the Common Attack Pattern Enumeration and Classification (CAPEC). It describes a recurring method attackers use to exploit software weaknesses.
How the attack works
The phases an attacker typically follows.
- Step 1Explore
[Survey application] The attacker takes an inventory of the entry points of the application.
- Spider web sites for all available links
- Sniff network communications with application using a utility such as WireShark.
- Step 2Experiment
[Determine user-controllable input susceptible to LDAP injection] For each user-controllable input that the attacker suspects is vulnerable to LDAP injection, attempt to inject characters that have special meaning in LDAP (such as a single quote character, etc.). The goal is to create a LDAP query with an invalid syntax
- Use web browser to inject input through text fields or through HTTP GET parameters
- Use a web application debugging tool such as Tamper Data, TamperIE, WebScarab,etc. to modify HTTP POST parameters, hidden fields, non-freeform fields, or other HTTP header.
- Use modified client (modified by reverse engineering) to inject input.
- Step 3Experiment
[Try to exploit the LDAP injection vulnerability] After determining that a given input is vulnerable to LDAP Injection, hypothesize what the underlying query looks like. Possibly using a tool, iteratively try to add logic to the query to extract information from the LDAP, or to modify or delete information in the LDAP.
- Add logic to the LDAP query to change the meaning of that command. Automated tools could be used to generate the LDAP injection strings.
- Use a web application debugging tool such as Tamper Data, TamperIE, WebScarab,etc. to modify HTTP POST parameters, hidden fields, non-freeform fields, or other HTTP header.
What the attacker needs
Prerequisites
- 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.
Skills required
- Medium skill: The attacker needs to have knowledge of LDAP, especially its query syntax.
Consequences
What a successful CAPEC-136 attack can achieve.
Unreliable Execution
Affects: Availability
Modify Data
Affects: Integrity
Read Data
Affects: Confidentiality
Execute Unauthorized Commands
Affects: Authorization
Run Arbitrary Code
Gain Privileges
Affects: Accountability, Authentication, Authorization, Non-Repudiation
Bypass Protection Mechanism
Affects: Access Control, Authorization
How to mitigate it
Defenses that reduce the risk of CAPEC-136.
- Strong input validation - All user-controllable input must be validated and filtered for illegal characters as well as LDAP content.
- Use of custom error pages - Attackers can glean information about the nature of queries from descriptive error messages. Input validation must be coupled with customized error pages that inform about an error without disclosing information about the LDAP or application.
Examples
PowerDNS before 2.9.18, when running with an LDAP backend, does not properly escape LDAP queries, which allows remote attackers to cause a denial of service (failure to answer ldap questions) and possibly conduct an LDAP injection attack. See also: CVE-2005-2301
Terminology & mappings
Mapped taxonomies
- WASC: LDAP Injection (29)
- OWASP Attacks: LDAP Injection
Frequently asked questions
Common questions about CAPEC-136.
- What is CAPEC-136?
- 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.
- How does a LDAP Injection attack work?
- It typically unfolds over 3 phases. It begins with: [Survey application] The attacker takes an inventory of the entry points of the application.
- How do you prevent CAPEC-136?
- Strong input validation - All user-controllable input must be validated and filtered for illegal characters as well as LDAP content.
- What weaknesses does CAPEC-136 target?
- CAPEC-136 exploits 3 CWE weaknesses: CWE-20 (Improper Input Validation), CWE-77 (Improper Neutralization of Special Elements used in a Command) and CWE-90 (Improper Neutralization of Special Elements used in an LDAP Query).
- How severe is CAPEC-136?
- MITRE rates CAPEC-136 as High severity with high likelihood of attack.
Sources
References
Attack-pattern data is sourced from the MITRE CAPEC catalog (v3.9). Weakness associations link to the corresponding CWE entries on RadicalNotion.AI.
Defend against CAPEC-136
Track the CVEs and weaknesses this technique exploits, with AI-written analysis and remediation steps.