Monthly Archives: July 2016

Manual Exploitation of Blind HQL Injections

Almost everyone has heard about SQL injections, but what about HQL injections? Hibernate Query Language (HQL) is an object-oriented query language, similar to Structured Query Language (SQL), but instead of operating on tables and columns, HQL works with persistent objects and their properties.

Imagine that you are doing a source-code review on a Java-based web application that uses Direct Web Remoting (DWR) and you come across the following line of code:

String statement = "select x from Rights x, Roles y where x.uId = y.uId " + "and y.roleId = " + rId;
List roles = DataUtils.getHQL().queryList(statement);

The ‘rId’ variable in the statement is taken directly from user input, thus making this line of code vulnerable. After tracing the ‘rId’ variable, it was found that the function that calls the vulnerable statement is also conveniently exposed via DWR. If you have not heard about DWR, it is a library that allows Java methods / functions to be exposed and called directly using JavaScript. (more info available here:

Using the JavaScript console in a web browser, it was possible to trigger the function call using the following command:


Note: The function names depends on how the developer of the web application implements the DWR library. One way to determine this is to observe the traffic through a proxy and look for the main DWR call that pulls the exposed functions’ JavaScript .js file. Take the JavaScript content of the file and manually load it in the browser console, so that you will be able to call the functions.

Calling the following exposed DWR call via JavaScript with the following parameter returns a response of Content-Length: 120:

DWRAction.getUserRightsByRoleID("1 or 1=2");

While calling the following exposed DWR call via JavaScript with the following parameter returns a response of Content-Length: 2649040:

DWRAction.getUserRightsByRoleID("1 or 1=1");

This looks like a confirmed case of a blind HQL injection vulnerability. The goal now would be to dump some important information from the database. Attempts were made to use SQLmap as well as an obscure HQLmap tool from GitHub, but they were not successful. Attempts were then made to exploit this vulnerability manually.

While playing with the injection parameters, it was observed that UNION queries were not allowed. Also, <, >, !, = comparators are filtered by the XSS filters. Single and double quotes were also filtered. You might ask why is the “1 or 1=1” input allowed with quotes? The reason behind this is because the exposed JavaScript DWR method takes in a String, therefore it has be sent to the server enclosed in quotes [DWRAction.getUserRightsByRoleID(String);].

Consulting the official HQL manual shows that the following expressions are supported:


After a bit of trial and error with the supported expressions, it was observed that the accepted inputs are:

  • ( ) Parentheses
  • Between x and y (this will be the alternative to < > comparators)
  • Sub SELECT statements allowed (alternative to UNION)

With this knowledge, the next step would be to find out valid tables and columns. Searching through the source code for other HQL statements gave some idea of what tables and columns exists. In this case, the table name was ‘TBL_USERS’ with several columns, but what we are interested in is just the “password” and “uId” columns.

The first step in order to extract some meaningful data will require a valid ‘uId’ from the ‘TBL_USERS’ table. The following sub SELECT payload was used:

DWRAction.getUserRightsByRoleID("1 or (select id from TBL_USERS where id between 1 and 2000) = 1");

After tweaking the ‘between’ values manually by elimination and looking at the server responses, it was observed that the ‘uId’ of value 1900 exists. Now, its time to get the password hash for the user who has the ‘uId’ value of 1900. One way to determine the characters of the password is to use ASCII comparison, and we will start with the first character of the password column using the following payload:

DWRAction.getUserRightsByRoleID("1 or (select ascii(substr(password,1,1)) from TBL_USERS where id = 1900) between [ASCII value] and [ASCII value]");

The ASCII values can be obtained from the chart below:


This part gets repetitive as the trial and error process begins. After many tries using elimination by tweaking the ‘between’ ASCII values, we now know the first character is an ASCII value of 49 which is equivalent to ‘1’. Repeat this tedious process till the n character by altering the substr() parameter in the statement. You can make the process less manual by using Burp Intruder and observing the responses.

Update: After knowing that its a hash value from the first few characters, the statement can be simplified to:

DWRAction.getUserRightsByRoleID("1 or (select ascii(substr(password,1,1)) from TBL_USERS where id = 1900) = [ASCII value]");

Where the ASCII value can range from 48 to 57 and 97 to 122. (Thanks @gifted88 for the tip.)

After all the hard work, the password hash for the user with “uId” 1900 is:


Post-Exploitation with Windows PowerShell

I gave a presentation on the topic of “Post-Exploitation with Windows PowerShell” sometime ago in 2015. This presentation showcases the use of PowerShell scripting exploitation frameworks coupled with various penetration testing tools and AV evasion techniques for post-exploitation on compromised hosts.

The slides can be found here:

Video of the demo from the presentation:

Trà Đá Hacking #1- FRP Remote Root

I recently spoke at Trà Đá Hacking #1 (, organized by VNSec in HCMC on the topic of ‘How to Get Started in Finding 0-Days – A Use Case’. The short introductory talk was intended to introduce the topic of finding 0-days using a real-world scenario as an example.

The slides can be found here:

I have created a remote code/command execution exploit client for the talk, based on 2 vulnerabilities discovered last year. The exploit can be downloaded here:

A sample video of the exploit in action:

Update: After a long time, the guys at FRP finally released the fixed version: