Difference between revisions of "Blind XPath Injection"

Jump to: navigation, search
(Simple XPath Injection)
(Blind XPath Injection)
Line 37: Line 37:
===Blind XPath Injection===
===Blind XPath Injection===
Using Blind XPath Injection, an attacker can extract a complete XML document for XPath querying without prior knowledge of the query. The attacker can access the entire XML "database" used in the XPath query which can be powerful against sites that use XPath queries (and XML "databases") for authentication, searching and other uses.
==Examples ==
==Examples ==

Revision as of 15:27, 8 September 2006

This is an Attack. To view all attacks, please see the Attack Category page.

This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.


About XPath

XPath is a sort 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. [1]

Simple XPath Injection

Before you can understand what Blind XPath Injection is, you must first have a basic understanding of Simple XPath Injection. So, lets suppose an application includes the following ASP.NET and C# source code:

 XmlDocument XmlDoc = new XmlDocument();
 XPathNavigator nav = XmlDoc.CreateNavigator();
 XPathExpression expr = nav.Compile("string(//user[name/text()='"+UserID.Text+
    "' and password/text()='"+Password.Text+
 String account=Convert.ToString(nav.Evaluate(expr));
 if (account=="")
 // Login failed - UserUD and password pair could not be found in the XML document 
 // Login succeeded - UserID and Password validated

Based on the way this sample code is written, an attacker could try to inject an XPath expression into the UserID text field. For example, the attacker could enter the following text into the UserID text field (just like with SQL injection):

' or 1=1 or ='

If this entry is not handled properly by the application, then the application will return the first account number in the XML document. If that occurs, the attacker will be logged in as the first user listed in the XML document.

Blind XPath Injection


Related Threats

Related Attacks

Related Vulnerabilities

Related Countermeasures