This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Difference between revisions of "Testing for LDAP Injection (OTG-INPVAL-006)"

Jump to: navigation, search
(Reverting to last version not containing links to
Line 1: Line 1:
[ asian babe cute ] [ quebec autoroutes ] [ autosurf site for sale] [ ancient greek clothing that aspasia wore ] [ australian vets for pfizer] [ addison automation force in sales ] [ download norton antivirus updates ] [ positive cash flow property australia ] [ canastasia studio pinpines ] [ unitrend auto insurance ] [ lu1848 norton antivirus ] [ 2004 cpi australia ] [ european african middle eastern theater ribbon ] [ asia fhm girl ] [ index] [ automatic shut off valve ] [ auto quirk ] [ jewelry news asia ] [ african bubble butt ] [ african scholarships ] [ panda titanium antivirus plus ] [ african marriage ritual ] [ inoculateit antivirus avboot ] [ kasperskys antivirus firewall ] [ asian healing arts ] [ abu australian photo ] [ pc magazine antivirus ] [ domain] [ starting samba automatically ] [ autocad blocks cars ] [ norten antivirus download ] [ webmap] [ network antivirus scanner ] [ australia driving map ] [ african penguin habitat ] [ link] [ antivirus server 2003 free ] [ antivirus software for pc ] [ american automobile racing association inc ] [ auto copart sale] [ stinger antivirus download free ] [ africas best universities ] [ pc cillin antivirus ] [ auto in law lemon mold ] [ panda antivirus free download ] [ panda antivirus free download ] [ antivirus free trial download ] [ asian tsunami blogs ] [ australian surf lifesaving titles 2004 photos ] [ lyrics to fantasia barrino ] 
{{Template:OWASP Testing Guide v3}}
{{Template:OWASP Testing Guide v3}}

Revision as of 12:50, 3 June 2009

OWASP Testing Guide v3 Table of Contents

This article is part of the OWASP Testing Guide v3. The entire OWASP Testing Guide v3 can be downloaded here.

OWASP at the moment is working at the OWASP Testing Guide v4: you can browse the Guide here

Brief Summary

LDAP is an acronym for Lightweight Directory Access Protocol. LDAP is a protocol to store information about users, hosts, and many other objects. LDAP injection is a server side attack, which could allow sensitive information about users and hosts represented in an LDAP structure to be disclosed, modified, or inserted.
This is done by manipulating input parameters afterwards passed to internal search, add, and modify functions.

Description of the Issue

A web application could use LDAP in order to let users authenticate or search other users' information inside a corporate structure.

The goal of LDAP injection attacks is to inject LDAP search filters metacharacters in a query which will be executed by the application.

[Rfc2254] defines a grammar on how to build a search filter on LDAPv3 and extends [Rfc1960] (LDAPv2).

An LDAP search filter is constructed in Polish notation, also known as [prefix notation].

This means that a pseudo code condition on a search filter like this:

find("cn=John & userPassword=mypass")

will be represented as:


Boolean conditions and group aggregations on an LDAP search filter could be applied by using the following metacharacters:

Metachar Meaning
& Boolean AND
| Boolean OR
 ! Boolean NOT
= Equals
~= Approx
>= Greater than
<= Less than
* Any character
() Grouping parenthesis

More complete examples on how to build a search filter can be found in the related RFC.

A successful exploitation of an LDAP injection vulnerability could allow the tester to:

  • Access unauthorized content
  • Evade application restrictions
  • Gather unauthorized informations
  • Add or modify Objects inside LDAP tree structure.

Black Box testing and example

Example 1. Search Filters

Let's suppose we have a web application using a search filter like the following one:


which is instantiated by an HTTP request like this:

If the value 'John' is replaced with a '*', by sending the request:*

the filter will look like:


which matches every object with a 'cn' attribute equals to anything.

If the application is vulnerable to LDAP injection, it will display some or all of the users' attributes, depending on the application's execution flow and the permissions of the LDAP connected user.

A tester could use a trial-and-error approach, by inserting in the parameter '(', '|', '&', '*' and the other characters, in order to check the application for errors.

Example 2. Login

If a web application uses LDAP to check user credentials during the login process and it is vulnerable to LDAP injection, it is possible to bypass the authentication check by injecting an always true LDAP query (in a similar way to SQL and XPATH injection ).

Let's suppose a web application uses a filter to match LDAP user/password pair.

searchlogin= "(&(uid="+user+")(userPassword={MD5}"+base64(pack("H*",md5(pass)))+"))";

By using the following values:


the search filter will results in:


which is correct and always true. This way, the tester will gain logged-in status as the first user in LDAP tree.


Sacha Faust: "LDAP Injection" -
Bruce Greenblatt: "LDAP Overview" -
IBM paper: "Understanding LDAP" -

Softerra LDAP Browser -