<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Casaba Security &#187; XSS</title>
	<atom:link href="http://www.casaba.com/blog/tag/xss/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.casaba.com/blog</link>
	<description>Building and breaking software and robots</description>
	<lastBuildDate>Wed, 11 Jan 2012 18:08:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>List of characters for testing Unicode transformations and best-fit mapping to dangerous ASCII</title>
		<link>http://www.casaba.com/blog/2010/12/list-of-characters-for-testing-unicode-transformations-and-best-fit-mapping-to-dangerous-ascii/</link>
		<comments>http://www.casaba.com/blog/2010/12/list-of-characters-for-testing-unicode-transformations-and-best-fit-mapping-to-dangerous-ascii/#comments</comments>
		<pubDate>Mon, 20 Dec 2010 18:54:58 +0000</pubDate>
		<dc:creator>Chris Weber</dc:creator>
				<category><![CDATA[Security Testing]]></category>
		<category><![CDATA[Unicode]]></category>
		<category><![CDATA[bestfit]]></category>
		<category><![CDATA[SQL injection]]></category>
		<category><![CDATA[XSS]]></category>

		<guid isPermaLink="false">http://www.casaba.com/blog/?p=239</guid>
		<description><![CDATA[I&#8217;m attaching two CSV files for use in test cases and tools.  The uni2asc.csv contains all of the Unicode characters that map to something ASCII &#60; 0&#215;80.  The bestfit.csv  contains all of the known best-fit  mappings to dangerous ASCII between legacy charsets and Unicode. uni2asc.csv &#8211; for straight Unicode to Unicode mappings bestfit.csv &#8211; for [...]]]></description>
			<content:encoded><![CDATA[<div>
<p>I&#8217;m attaching two CSV files for use in test cases and tools.  The uni2asc.csv contains all of the Unicode characters that map to something ASCII &lt; 0&#215;80.  The bestfit.csv  contains all of the known best-fit  mappings to dangerous ASCII between legacy charsets and Unicode.</p>
<p><a href="http://www.lookout.net/wp-content/uploads/2010/12/uni2asc.csv">uni2asc.csv</a> &#8211; for straight Unicode to Unicode mappings<br />
<a href="http://www.lookout.net/wp-content/uploads/2010/12/bestfit.csv">bestfit.csv</a> &#8211; for legacy charset to Unicode mappings</p>
<p>I gave these to Gareth so they may wind up in <a href="http://hackvertor.co.uk/public">HackVertor</a>.</p>
<p>The Unicode database contains meta data about every character, including compatibility mappings, normalization mappings, case mappings, and other decomposition data.  It&#8217;s useful for testing to know what special Unicode characters may transform to dangerous ASCII.  For example:</p>
<ul>
<li>U+2134 SCRIPT SMALL O character will transform to the U+006F LATIN SMALL LETTER in certain cases</li>
</ul>
<p>Of course, if you&#8217;re testing for SQL injection or XSS you probably want to know what transforms to dangerous characters like &#8216; and &lt;.  We attempted to automate some of this in our <a href="http://xss.codeplex.com/">x5s tool</a> which has done a good job so far, and we have a big update for that coming soon.</p>
<p>In the bestfit.csv file you&#8217;ll find all of best-fit mappings from Unicode to dangerous ASCII &lt; 0&#215;80 (and vice versa) in many of the legacy charsets from <a href="http://unicode.org/Public/MAPPINGS/">http://unicode.org/Public/MAPPINGS/</a>.  There&#8217;s some wild legacy stuff in here.  For example:</p>
<ul>
<li>
<div id="_mcePaste">In APL-ISO-IR-68, 0&#215;27 maps to 0x5D in Unicode, and vice versa.</div>
</li>
</ul>
<p>If you put these to use anywhere please let me know so I can pass the word along.</p>
</div>
<p>In APL-ISO-IR-68, 0&#215;27 maps to 0x5D in Unicode, and vice versa.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.casaba.com/blog/2010/12/list-of-characters-for-testing-unicode-transformations-and-best-fit-mapping-to-dangerous-ascii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unibomber tool for specialized XSS testing</title>
		<link>http://www.casaba.com/blog/2009/07/unibomber-tool-for-specialized-xss-testing/</link>
		<comments>http://www.casaba.com/blog/2009/07/unibomber-tool-for-specialized-xss-testing/#comments</comments>
		<pubDate>Tue, 28 Jul 2009 01:04:31 +0000</pubDate>
		<dc:creator>Chris Weber</dc:creator>
				<category><![CDATA[Security Testing]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Unicode]]></category>
		<category><![CDATA[XSS]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[John Hernandez has been working hard at Casaba to build a specialized testing tool that automates some of the unique techniques we use to find cross-sites scripting bugs (XSS). At Black Hat I&#039;m planning to demo what we have so far. It automates the testing process greatly, by auto-injecting a canary and ID into each [...]]]></description>
			<content:encoded><![CDATA[<p>John Hernandez has been working hard at Casaba to build a specialized testing tool that automates some of the unique techniques we use to find cross-sites scripting bugs (XSS).  At Black Hat I&#039;m planning to demo what we have so far.  It automates the testing process greatly, by auto-injecting a canary and ID into each input be it query string, HTTP header, or POST parameter.  By combining injection with &#039;output encoding&#039; detection, you get automation that assists pen-testers in finding vulnerability hotspots.</p>
<p>Because it basically bombs a Web-app with a slew of Unicode characters to find XSS bugs we named it the <strong>Unibomber</strong>.</p>
<p>Appended to the canary is a special character &#8211; special because it can transform into a &#039;dangerous&#039; character through normalization, casing, or best-fit mapping operations.  So we end up injecting these special characters all over the place and then detecting where they get transformed and displayed as output.</p>
<p>The beauty is that we can find both reflected and persistent XSS bugs this way.  It&#039;s not a one-click tool though, this is intended for use by an experienced person who knows how to find and exploit a clever XSS bug.  </p>
<p>Anyone who looks for XSS will likely find some good bugs with the Unibomber.  We sure have!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.casaba.com/blog/2009/07/unibomber-tool-for-specialized-xss-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

