Difference between revisions of "Blind XPath Injection"
|Line 98:||Line 98:|
==Related [[Threat Agents]]==
==Related [[Threat Agents]]==
Revision as of 15:18, 12 September 2008
ASDR Table of Contents
Last revision (mm/dd/yy): 09/12/2008
XPath is a type of query language that describes how to locate specific elements (including attributes, processing instructions, etc.) in an XML document. Since it is a query language, XPath is somewhat similar to Structured Query Language (SQL). However, XPath can be used to reference almost any part of any XML document without access control restrictions, whereas with SQL, a "user" (which is a term undefined in the XPath/XML context) may be restricted to certain tables, columns or queries.
More information may be found in the article dedicated to XPATH Injection. Using an XPATH_Injection attack the attacker is able to log in to the system without entering valid login and password. If he wants to know information about other users he must take one step further. When conducting a Blind XPath Injection attack, the attacker has no knowledge about the structure of the XML document. However his situation is better compared to Blind_SQL_Injection, because there are functions which allow for performing tests (XML Crawling) and in the end getting to know the document structure.
The attacker may be successfull using two methods: Boolenization and XML Crawling. By adding to the XPath syntax, the attacker uses additional expressions (replacing what the attacker entered in the place of login to the specially crafted expression).
Using the "Boolenization" method the attacker may find out if the given XPath expression is True or False. Let's assume that the aim of the attacker is to log in to the account. Successfull log in would be equal "True" and failed log in attempt would equal "False". Only a smart portion of the information is analyzed "character" or the number. When the attacker focuses on the string he may reveal it in its entirety by checking every single character within the class/range of characters this string belongs to.
Using a string-length(S) function, where S is a string, the attacker may find out the length of this string. With the appropriate number of substring(S,N,1) function iterations, where S is a previously mentioned string, N is a start character, and "1" is a next character counting from N character, the attacker is able to find out the whole string.
<?xml version="1.0" encoding="UTF-8"?> <data> <user> <login>admin</login> <password>test</password> <realname>SuperUser</realname> </user> <user> <login>rezos</login> <password>rezos123</password> <realname>Simple User</realname> </user> </data>
- string.stringlength(//user[position()=1]/child::node()[position()=2]) returns the length of the second string of the first user (8),
- substring((//user[position()=1]/child::node()[position()=2),1,1) returns the first character of this user ('r').
To get to know the XML document structure the attacker may use:
This will return the number of nodes (in this case 2).
Using this query the attacker will find out if the second string (password) of the first node (user 'admin') consists of 6 characters.
- substring(string, number, number)
This query will confirm (True) or deny (False) that the first character of the user ('admin') password is an "a" character.
If the log in form would look like this:
String FindUser; FindUser = "//user[login/text()='" + Request("Username") + "' And password/text()='" + Request("Password") + "']";
then the attacker should inject the following code:
Username: ' or substring((//user[position()=1]/child::node()[position()=2]),1,1)="a" or ''='
The XPath syntax may remind you of common SQL_Injection attacks but the attacker must consider that this language disallows commenting out the rest of expresssion. To omit this limitation the attacker should use OR expressions to void all expressions, which may disrupt the attack.
Because of Boolenization the number of queries, even within a small XML document, may be very high (thousands, houndred of thousands and more). That is why this attack is not conducted manually. Knowing few basic XPath functions the attacker is able to write an application in a short time, which will rebuild the structure of the document and will fill it with data by itself.
Related Threat Agents
- http://www.modsecurity.org/archive/amit/blind-xpath-injection.pdf - by Amit Klein (much more detailes, in my opinion the best source about Blind XPath Injection).