<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Anatomy of an XSS exploit</title>
	<atom:link href="http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/</link>
	<description>Security Research, Computer Laboratory, University of Cambridge</description>
	<pubDate>Sun, 27 Jul 2008 09:14:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: miaw</title>
		<link>http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-23824</link>
		<dc:creator>miaw</dc:creator>
		<pubDate>Fri, 31 Aug 2007 04:25:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-23824</guid>
		<description>found xss
http://www.lightbluetouchpaper.org/index.php?s=%3Cscript%3Ealert%28%27xss%27%29%3C%2Fscript%3E&#38;searchbutton=Go%21

[Thanks for pointing this out. The bug has now been fixed -- Steven Murdoch]</description>
		<content:encoded><![CDATA[<p>found xss<br />
<a href="http://www.lightbluetouchpaper.org/index.php?s=%3Cscript%3Ealert%28%27xss%27%29%3C%2Fscript%3E&amp;searchbutton=Go%21" rel="nofollow">http://www.lightbluetouchpaper.org/index.php?s=%3Cscript%3Ealert%28%27xss%27%29%3C%2Fscript%3E&amp;searchbutton=Go%21</a></p>
<p>[Thanks for pointing this out. The bug has now been fixed -- Steven Murdoch]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Never Tell&#8230; &#187; Blog Archive &#187; links for 2006-06-28</title>
		<link>http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-661</link>
		<dc:creator>Never Tell&#8230; &#187; Blog Archive &#187; links for 2006-06-28</dc:creator>
		<pubDate>Sun, 02 Jul 2006 16:12:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-661</guid>
		<description>[...] Light Blue Touchpaper » Anatomy of an XSS exploit (tags: tech security) [...]</description>
		<content:encoded><![CDATA[<p>[...] Light Blue Touchpaper » Anatomy of an XSS exploit (tags: tech security) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew van der Stock</title>
		<link>http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-615</link>
		<dc:creator>Andrew van der Stock</dc:creator>
		<pubDate>Wed, 28 Jun 2006 04:11:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-615</guid>
		<description>Hi Steven,

so you're saying any PHP code which does this:
&lt;code&gt;
$clean = array();
$html = array();

$clean['userinput'] = trim(strip_tags($_POST['userinput']));
if ( strlen($clean['userinput']) &#60; 3 )
{
$html['warning'] = htmlspecialchars($lang['errMsgTooShort'] . $clean['userinput'], ENT_QUOTES, 'UTF-8');

echo &#34;&#60;html&#62;&#60;body&#62;&#60;script&#62;var text = '{$html['warning']}';&#60;/script&#62;&#34;;
echo &#34;&#60;script&#62;alert(text);&#60;/script&#62;&#60;/body&#62;&#60;/html&#62;&#34;;
exit;
}
// continue on...
&lt;/code&gt;

is at risk? What do you need to do to become safe? 

thanks,
Andrew
(OWASP Guide author :)</description>
		<content:encoded><![CDATA[<p>Hi Steven,</p>
<p>so you&#8217;re saying any PHP code which does this:<br />
<code><br />
$clean = array();<br />
$html = array();</p>
<p>$clean['userinput'] = trim(strip_tags($_POST['userinput']));<br />
if ( strlen($clean['userinput']) &lt; 3 )<br />
{<br />
$html['warning'] = htmlspecialchars($lang['errMsgTooShort'] . $clean['userinput'], ENT_QUOTES, &#8216;UTF-8&#8242;);</p>
<p>echo &quot;&lt;html&gt;&lt;body&gt;&lt;script&gt;var text = &#8216;{$html['warning']}&#8217;;&lt;/script&gt;&quot;;<br />
echo &quot;&lt;script&gt;alert(text);&lt;/script&gt;&lt;/body&gt;&lt;/html&gt;&quot;;<br />
exit;<br />
}<br />
// continue on&#8230;<br />
</code></p>
<p>is at risk? What do you need to do to become safe? </p>
<p>thanks,<br />
Andrew<br />
(OWASP Guide author <img src='http://www.lightbluetouchpaper.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Light Blue Touchpaper &#187; Oracle attack on Wordpress</title>
		<link>http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-599</link>
		<dc:creator>Light Blue Touchpaper &#187; Oracle attack on Wordpress</dc:creator>
		<pubDate>Thu, 22 Jun 2006 13:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-599</guid>
		<description>[...] This post describes the second of two vulnerabilities I found in Wordpress. The first, a XSS vulnerability, was described last week. While the vulnerability discussed here is applicable in fewer cases than the previous one, it is an example of a comparatively rare class, oracle attacks, so I think merits further exposition. [...]</description>
		<content:encoded><![CDATA[<p>[...] This post describes the second of two vulnerabilities I found in Wordpress. The first, a XSS vulnerability, was described last week. While the vulnerability discussed here is applicable in fewer cases than the previous one, it is an example of a comparatively rare class, oracle attacks, so I think merits further exposition. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven J. Murdoch</title>
		<link>http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-589</link>
		<dc:creator>Steven J. Murdoch</dc:creator>
		<pubDate>Thu, 15 Jun 2006 13:20:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-589</guid>
		<description>@Dave Armstrong

Thanks for the pointer.

I do know of some XSS worms (see comment 1), but the one I suggested is slightly different. It uses XSS as the infection vector, but propagation and payload code are run on the server. This reduces applicability to software like Wordpress which allows XSS to server compromise escalation, but the payload can do more (e.g. botnet creation).

A pure XSS worm might be possible with Wordpress, but the two limitations we found were the 255 character limit on author name, and the variety of ways themes render the blogroll. We couldn't see an easy way to find blogs to attack next, based only on the DOM tree in ~240 bytes of Javascript. However, if you can run PHP, the list can be trivially sucked from the database.</description>
		<content:encoded><![CDATA[<p>@Dave Armstrong</p>
<p>Thanks for the pointer.</p>
<p>I do know of some XSS worms (see comment 1), but the one I suggested is slightly different. It uses XSS as the infection vector, but propagation and payload code are run on the server. This reduces applicability to software like Wordpress which allows XSS to server compromise escalation, but the payload can do more (e.g. botnet creation).</p>
<p>A pure XSS worm might be possible with Wordpress, but the two limitations we found were the 255 character limit on author name, and the variety of ways themes render the blogroll. We couldn&#8217;t see an easy way to find blogs to attack next, based only on the DOM tree in ~240 bytes of Javascript. However, if you can run PHP, the list can be trivially sucked from the database.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Armstrong</title>
		<link>http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-588</link>
		<dc:creator>Dave Armstrong</dc:creator>
		<pubDate>Thu, 15 Jun 2006 12:55:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-588</guid>
		<description>XSS/Javascript worms are not a new concept:

http://www.bindshell.net/papers/xssv</description>
		<content:encoded><![CDATA[<p>XSS/Javascript worms are not a new concept:</p>
<p><a href="http://www.bindshell.net/papers/xssv" rel="nofollow">http://www.bindshell.net/papers/xssv</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven J. Murdoch</title>
		<link>http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-575</link>
		<dc:creator>Steven J. Murdoch</dc:creator>
		<pubDate>Tue, 13 Jun 2006 11:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/06/13/anatomy-of-an-xss-exploit/#comment-575</guid>
		<description>&lt;blockquote&gt;There has been a PHP worm before, but I don’t know of any XSS based ones.&lt;/blockquote&gt;

Just a few hours ago, F-secure &lt;a href="http://www.f-secure.com/v-descs/yamanner_a.shtml rel="nofollow" rel="nofollow" rel="nofollow" rel="nofollow"&gt;blogged about&lt;/a&gt; a Javascript worm. Although there aren't many details, it looks like it's exploiting an XSS bug in Yahoo Mail. This also reminded me of the &lt;a href="http://www.theregister.co.uk/2005/10/17/web20_worm_knocks_out_myspaces/" rel="nofollow" rel="nofollow"&gt;MySpace worm&lt;/a&gt;.

I still am not aware of any worm which runs code both on the server and client, which would be the likely operation of my hypothesised Wordpress XSS one.</description>
		<content:encoded><![CDATA[<blockquote><p>There has been a PHP worm before, but I don’t know of any XSS based ones.</p></blockquote>
<p>Just a few hours ago, F-secure <a href="http://www.f-secure.com/v-descs/yamanner_a.shtml rel="nofollow" rel="nofollow" rel="nofollow" rel="nofollow">blogged about</a> a Javascript worm. Although there aren&#8217;t many details, it looks like it&#8217;s exploiting an XSS bug in Yahoo Mail. This also reminded me of the <a href="http://www.theregister.co.uk/2005/10/17/web20_worm_knocks_out_myspaces/" rel="nofollow" rel="nofollow">MySpace worm</a>.</p>
<p>I still am not aware of any worm which runs code both on the server and client, which would be the likely operation of my hypothesised Wordpress XSS one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
