Difference between revisions of "Alternate XSS Syntax"

From OWASP
Jump to: navigation, search
m (Categories)
(adjustments to new template)
Line 1: Line 1:
 
{{Template:Attack}}
 
{{Template:Attack}}
 +
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
 
==Description==
 
==Description==
Line 39: Line 41:
  
  
==Examples ==
+
==Risk Factors==
  
Example 1 ('''XSS using Script in Attributes''')
 
  
 +
 +
==Examples ==
 +
 +
===XSS using Script in Attributes===
  
 
XSS attacks may be conducted without using <script></script> tags.
 
XSS attacks may be conducted without using <script></script> tags.
Line 61: Line 66:
  
  
Example 2 ('''XSS using Script Via Encoded URI Schemes''')
+
===XSS using Script Via Encoded URI Schemes===
  
 
If we need to hide against web application filters we may try to encode string characters, e.g.: a=&#X41 (UTF-8) and use it in
 
If we need to hide against web application filters we may try to encode string characters, e.g.: a=&#X41 (UTF-8) and use it in
Line 71: Line 76:
  
  
Example 3 ('''XSS using code encoding''')
+
===XSS using code encoding===
 
+
  
 
We may encode our script in base64 and place it in META tag. This way we get rid of alert() totally. More information about this method can be found in RFC 2397
 
We may encode our script in base64 and place it in META tag. This way we get rid of alert() totally. More information about this method can be found in RFC 2397
Line 82: Line 86:
  
  
References:
+
==Related [[Threat Agents]]==
* http://ha.ckers.org/xss.html
+
* http://www.businessinfo.co.uk/labs/hackvertor/hackvertor.php
+
  
 +
* [[Client-side_Attacks]]
  
==Related Threats==
 
  
*[[Client-side_Attacks]]
+
==Related [[Attacks]]==
  
==Related Attacks==
+
* [[Cross_Site_Scripting]]
 +
* [[Category:Injection Attack]]
 +
* [[Invoking untrusted mobile code]]
  
*[[Cross_Site_Scripting]]
 
*[[Category:Injection Attack]]
 
*[[Invoking untrusted mobile code]]
 
  
==Related Vulnerabilities==
+
==Related [[Vulnerabilities]]==
  
*[[:Category:Input Validation Vulnerability]]
+
* [[:Category:Input Validation Vulnerability]]
  
==Related Countermeasures==
 
  
[[HTML Entity Encoding]]
+
==Related [[Controls]]==
  
Use whitelists and if it's possible specify detailed format of the expected output data.
+
* [[HTML Entity Encoding]]
 +
* Use whitelists and if it's possible specify detailed format of the expected output data.
  
==Categories==
 
  
[[Category:Injection]]
+
==References==
 +
* http://ha.ckers.org/xss.html
 +
* http://www.businessinfo.co.uk/labs/hackvertor/hackvertor.php
  
[[Category:Attack]]
+
 
 +
[[Category:Abuse of Functionality]]
 +
[[Category:Embedded Malicious Code]]
 +
[[Category:Injection]]

Revision as of 10:32, 15 June 2008

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


Last revision (mm/dd/yy): 06/15/2008

Description

Cross Site Scripting is not just <script>alert('y0u ar3 0wn3d!');</script>. Because of JavaScript and HTML flexibility and their interpretation by the web browsers, it's possible to achive the same goal in many different ways. In effect we may try to bypass more or less successful input data filtering methods. Conducting a ssuccessfull attack depeneds on the web browsers used by the attacker (when he's building XSS) and the victim.

Some JS and HTML constructions after encoding are correctly interpreted by some browsers, nontheless it often varies on the web browser version, and others are not.

If we want to use popular <script> tags anyway, we may try to bypass filtering replacing given characters with their equivalents:

From To

<    <

> >  >

(    (

)    )

#    #

&    &

"    "

In this case:

 <script>alert('y0u ar3 0wn3d!');</script>

would be replaced with:

&\lt;script&\gt;alert&\#40;'y0u ar3 0wn3d!'&\#41;;&\lt;/script&\gt;

However there are browsers which will automatically reverse the process and interpret this string correctly.

We don't need to do replacement at all, we may get the same effect in many different ways.


Risk Factors

Examples

XSS using Script in Attributes

XSS attacks may be conducted without using <script></script> tags. Other tags will do exacly the same thing, e.g.:

<body onload=alert('test1')>

or other attribites like: onmouseover, onerror.

onmouseover

<b onmouseover=alert('Wufff!')>click me!</b>

onerror

<img src="http://url.to.file.which/not.exist" onerror=alert(document.cookie);>


XSS using Script Via Encoded URI Schemes

If we need to hide against web application filters we may try to encode string characters, e.g.: a=&#X41 (UTF-8) and use it in IMG tag:

<IMG SRC=j&#X41vascript:alert('test2')>

There are many different UTF-8 encoding notations what give us even more possibilities.


XSS using code encoding

We may encode our script in base64 and place it in META tag. This way we get rid of alert() totally. More information about this method can be found in RFC 2397

<META HTTP-EQUIV="refresh"
CONTENT="0;url=data:text/html;base64,PHNjcmlwdD5hbGVydCgndGVzdDMnKTwvc2NyaXB0Pg">

These (just a little modified by me) and others examples can be found on http://ha.ckers.org/xss.html, which is a true encyclopedia of the alternate XSS syntax attack.


Related Threat Agents


Related Attacks


Related Vulnerabilities


Related Controls

  • HTML Entity Encoding
  • Use whitelists and if it's possible specify detailed format of the expected output data.


References