Python - Ldap Injection - harder

Running the app on Docker

$ sudo docker pull blabla1337/owasp-skf-lab:ldap-injection-harder

$ sudo docker run -ti -p 127.0.0.1:5000:5000 blabla1337/owasp-skf-lab:ldap-injection-harder

Now that the app is running let's go hacking!

Reconnaissance

LDAP Injection is an attack used to exploit web based applications that construct LDAP statements based on user input. When an application fails to properly sanitize user input, it’s possible to modify LDAP statements using a local proxy. This could result in the execution of arbitrary commands such as granting permissions to unauthorized queries, and content modification inside the LDAP tree. The same advanced exploitation techniques available in SQL Injection can be similarly applied in LDAP Injection.

Let's open the app.

Trying to loggin with a random username and password.

The application architecture that supports LDAP includes both server-side and client-side components. The LDAP queries submitted to the server are known as LDAP search filters, which are constructed using prefix notation. Below is an example of an LDAP search filter:

find("(&(cn=" + username +")(userPassword=" + pass +"))")

This prefix filter notation instructs the query to find an LDAP node with the given username and password.

Exploitation

Let's check the app.js file.

search_filter = "(&(cn="+username+")(sn="+password+"))"

We can see that the filter is constructed by concatenating the username and password directly into the filter without proper sanitization. If we replace the username and password with a special character we can bypass authentication controls. Using * as the username and password will result in a successful login.

search_filter = "(&(cn=" * ")(sn=" * "))";

No luck, maybe this application is sanitizing the user input somehow, let's check the code again.

if(len(secret) < 2):
	return render_template("index.html", result = "The secret answer is at least 2 character long.")

The approach here to avoid LdaP injection was to check for the length of the user input. If the length is less than 2, the user input is invalid. Unfortunately for the developer, this approach is not very secure. Special characters other than "*" can also be used to create malicious queries.

username = admin)(!(&(1=0
password = q))

We successfully logged in as the Admin.

Additional sources

LDAP Injection | OWASP Foundationowasp.org

LDAP Injection Prevention - OWASP Cheat Sheet Seriescheatsheetseries.owasp.org

What Is LDAP Injection and How Does It Work? | Black Duckblackduck_sw

PayloadsAllTheThings/LDAP Injection/README.md at master · swisskyrepo/PayloadsAllTheThingsGitHub