Testing for LDAP Injection (OTG-INPVAL-006)

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

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:

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

Boolean conditions and group aggregations on an LDAP search filter could be applied by using the following metacharacters: 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.

Example 1. Search Filters
Let's suppose we have a web application using a search filter like the following one:

searchfilter="(cn="+user+")"

which is instantiated by an HTTP request like this:

http://www.example.com/ldapsearch?user=John

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

http://www.example.com/ldapsearch?user=*

the filter will look like:

searchfilter="(cn=*)"

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:

user=*)(uid=*))(|(uid=* pass=password

the search filter will results in:

searchlogin="(&(uid=*)(uid=*))(|(uid=*)(userPassword={MD5}X03MO1qnZdYdgyfeuILPmQ==))";

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