<?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>Chris Kite &#187; xss</title>
	<atom:link href="http://www.chriskite.com/tag/xss/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chriskite.com</link>
	<description>Programming, Computer Security, Etc.</description>
	<lastBuildDate>Wed, 24 Jun 2009 02:28:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>More Trouble with Twitter: The StalkDaily Worm</title>
		<link>http://www.chriskite.com/2009/04/12/more-trouble-with-twitter-the-stalkdaily-worm/</link>
		<comments>http://www.chriskite.com/2009/04/12/more-trouble-with-twitter-the-stalkdaily-worm/#comments</comments>
		<pubDate>Mon, 13 Apr 2009 03:38:46 +0000</pubDate>
		<dc:creator>Chris Kite</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Web Applications]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[xss]]></category>

		<guid isPermaLink="false">http://www.chriskite.com/?p=55</guid>
		<description><![CDATA[Twitter has had a lot of embarrassing security problems in the past, but the worst part is that they still haven&#8217;t learned from their mistakes. Apparently a recent redesign left the profile page vulnerable to a very simple XSS attack.
Some enterprising hacker quickly seized the opportunity to promote Twitter-clone StalkDaily by infecting the profiles of [...]]]></description>
			<content:encoded><![CDATA[<p>Twitter has had a lot of embarrassing security problems in the past, but the worst part is that they still haven&#8217;t learned from their mistakes. Apparently a recent redesign left the profile page vulnerable to a very simple XSS attack.</p>
<p>Some enterprising hacker quickly seized the opportunity to promote Twitter-clone StalkDaily by infecting the profiles of hundreds of users, and using their accounts to Tweet marketing messages such as &#8220;Join www.StalkDaily.com everyone!&#8221;. StalkDaily denies any responsibility for the XSS attack. The <a href="http://gist.github.com/93782" target="_blank">source-code for the worm</a> is available, and reveals just how simple this attack really was.</p>
<p>Here is a little free advice for the developers at Twitter: install <a href="http://github.com/jamestyj/xss-shield/tree/master" target="_blank">xss-shield</a>, or start using h() to escape user-supplied strings in your templates. Since the field that was vulnerable to cross-site scripting and allowed this worm to propogate was supposed to be a URL, it might not hurt to validate that against a simple regular expression while you&#8217;re at it.</p>
<p>I&#8217;ve lost count of the number of security breaches Twitter has had in the past few months. The question now is whether they&#8217;ll hire a competent web security architect and clean-up their act.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.chriskite.com/2009/04/12/more-trouble-with-twitter-the-stalkdaily-worm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
