<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: A Yahoo Mail Ajax Worm?</title>
	<atom:link href="http://ajaxian.com/archives/a-yahoo-mail-ajax-worm/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/a-yahoo-mail-ajax-worm</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: Web 2.0</title>
		<link>http://ajaxian.com/archives/a-yahoo-mail-ajax-worm/comment-page-1#comment-29948</link>
		<dc:creator>Web 2.0</dc:creator>
		<pubDate>Sun, 18 Jun 2006 13:50:19 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/a-yahoo-mail-ajax-worm#comment-29948</guid>
		<description>&lt;strong&gt;Vulnerability 2.0 : Worms in our web&lt;/strong&gt;

As web 2.0 sites are growing up, common side effects of grown-up software are coming along. First sign was the worm that attacked MySpace.com last year. Only a week ago Yahoo! Mail was attacked by a javascript worm. Some argue...</description>
		<content:encoded><![CDATA[<p><strong>Vulnerability 2.0 : Worms in our web</strong></p>
<p>As web 2.0 sites are growing up, common side effects of grown-up software are coming along. First sign was the worm that attacked MySpace.com last year. Only a week ago Yahoo! Mail was attacked by a javascript worm. Some argue&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: strimble</title>
		<link>http://ajaxian.com/archives/a-yahoo-mail-ajax-worm/comment-page-1#comment-27450</link>
		<dc:creator>strimble</dc:creator>
		<pubDate>Thu, 15 Jun 2006 01:22:16 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/a-yahoo-mail-ajax-worm#comment-27450</guid>
		<description>I mentioned this the other day on my blog also.  I actually received the malicious email.  The subject line said &#039;New Graphic Site&#039;.

Anyone need an invitation to Gmail?</description>
		<content:encoded><![CDATA[<p>I mentioned this the other day on my blog also.  I actually received the malicious email.  The subject line said &#8216;New Graphic Site&#8217;.</p>
<p>Anyone need an invitation to Gmail?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Per A. Noid</title>
		<link>http://ajaxian.com/archives/a-yahoo-mail-ajax-worm/comment-page-1#comment-27400</link>
		<dc:creator>Per A. Noid</dc:creator>
		<pubDate>Wed, 14 Jun 2006 22:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/a-yahoo-mail-ajax-worm#comment-27400</guid>
		<description>Any HTML page is subject to code insertion right?  That&#039;s not new to ajax.    Server-side check and validate anything from the Web.  We learned that with CGI in 1995.  

Granted an efficiency of this attack was the fact that the address book could data be retrieved easily, lowering the bar over how inserted code could otherwise get addresses in a non-ajax Web based email program as well and spoof submissions to the web interface to the SMTP process. (It just would do it more slowly with lots more request response). 

Seems that Yahoo!&#039;s exposure was more related to the fact that it had an email service exposed over HTTP and thus enabled information to propagate to others via the email service in the domain and leave the domain via the web api to its SMTP processes.  Since XHR disallows cross sub-domain data exchange, and even iframes disallow cross domain data access, the real hole here was the HTTP service that allowed mail to be sent, unverified -- a server side implementation issue more than an inherent problem in XHR, JavaScript, or XML.

Isnâ€™t that a pretty narrow case?  EG.  If youâ€™re not making web based email services this kind of security loop hole would not pertain?</description>
		<content:encoded><![CDATA[<p>Any HTML page is subject to code insertion right?  That&#8217;s not new to ajax.    Server-side check and validate anything from the Web.  We learned that with CGI in 1995.  </p>
<p>Granted an efficiency of this attack was the fact that the address book could data be retrieved easily, lowering the bar over how inserted code could otherwise get addresses in a non-ajax Web based email program as well and spoof submissions to the web interface to the SMTP process. (It just would do it more slowly with lots more request response). </p>
<p>Seems that Yahoo!&#8217;s exposure was more related to the fact that it had an email service exposed over HTTP and thus enabled information to propagate to others via the email service in the domain and leave the domain via the web api to its SMTP processes.  Since XHR disallows cross sub-domain data exchange, and even iframes disallow cross domain data access, the real hole here was the HTTP service that allowed mail to be sent, unverified &#8212; a server side implementation issue more than an inherent problem in XHR, JavaScript, or XML.</p>
<p>Isnâ€™t that a pretty narrow case?  EG.  If youâ€™re not making web based email services this kind of security loop hole would not pertain?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Berend de Boer</title>
		<link>http://ajaxian.com/archives/a-yahoo-mail-ajax-worm/comment-page-1#comment-27395</link>
		<dc:creator>Berend de Boer</dc:creator>
		<pubDate>Wed, 14 Jun 2006 22:36:51 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/a-yahoo-mail-ajax-worm#comment-27395</guid>
		<description>How do you actually clear user input 100%? Is there a definitive, and provably correct, overview of how to make sure all malicious input in an input field is cleared?</description>
		<content:encoded><![CDATA[<p>How do you actually clear user input 100%? Is there a definitive, and provably correct, overview of how to make sure all malicious input in an input field is cleared?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Schiller</title>
		<link>http://ajaxian.com/archives/a-yahoo-mail-ajax-worm/comment-page-1#comment-27207</link>
		<dc:creator>Scott Schiller</dc:creator>
		<pubDate>Wed, 14 Jun 2006 15:58:04 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/a-yahoo-mail-ajax-worm#comment-27207</guid>
		<description>I was looking at the source of this on Monday morning, laughing and saying &quot;This thing uses XHR, it&#039;s an Ajax &#039;worm&#039;! Someone call up the Ajaxian.com guys, quick!&quot; ;) We laughed and left it at that, but it&#039;s nice to see it actually getting a mention. With all the interest and hype around it, it should be mentioned that it has its potential dangers as well. While not new (you could set an img .src attribute to request data from any server), the added ability to parse XHR responses makes it potentially more dangerous.</description>
		<content:encoded><![CDATA[<p>I was looking at the source of this on Monday morning, laughing and saying &#8220;This thing uses XHR, it&#8217;s an Ajax &#8216;worm&#8217;! Someone call up the Ajaxian.com guys, quick!&#8221; ;) We laughed and left it at that, but it&#8217;s nice to see it actually getting a mention. With all the interest and hype around it, it should be mentioned that it has its potential dangers as well. While not new (you could set an img .src attribute to request data from any server), the added ability to parse XHR responses makes it potentially more dangerous.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IT Eclectic &#187; Blog Archive &#187; Today&#8217;s Web 2.0 digest</title>
		<link>http://ajaxian.com/archives/a-yahoo-mail-ajax-worm/comment-page-1#comment-27199</link>
		<dc:creator>IT Eclectic &#187; Blog Archive &#187; Today&#8217;s Web 2.0 digest</dc:creator>
		<pubDate>Wed, 14 Jun 2006 15:35:30 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/a-yahoo-mail-ajax-worm#comment-27199</guid>
		<description>[...] An axe to grind with Ajax [Ajaxian] A Yahoo Mail Ajax Worm? [Ajaxian] Java and Ajax Webinar [Ajaxian] Google Ajax Search API [Ajaxian] [...]</description>
		<content:encoded><![CDATA[<p>[...] An axe to grind with Ajax [Ajaxian] A Yahoo Mail Ajax Worm? [Ajaxian] Java and Ajax Webinar [Ajaxian] Google Ajax Search API [Ajaxian] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Grossberg</title>
		<link>http://ajaxian.com/archives/a-yahoo-mail-ajax-worm/comment-page-1#comment-27173</link>
		<dc:creator>Joe Grossberg</dc:creator>
		<pubDate>Wed, 14 Jun 2006 14:44:51 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/a-yahoo-mail-ajax-worm#comment-27173</guid>
		<description>&lt;strong&gt;Yahoo! Mail Worm&lt;/strong&gt;

The Yahoo! worm I mentioned earlier uses Ajax to harvest those email addresses. Ajaxian has the (safely-viewable) source code. Interesting....</description>
		<content:encoded><![CDATA[<p><strong>Yahoo! Mail Worm</strong></p>
<p>The Yahoo! worm I mentioned earlier uses Ajax to harvest those email addresses. Ajaxian has the (safely-viewable) source code. Interesting&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

