<?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: XSS for Fun and Profit</title>
	<atom:link href="http://michaeldaw.org/papers/paper-290507/feed" rel="self" type="application/rss+xml" />
	<link>http://michaeldaw.org/papers/paper-290507</link>
	<description>Weekly humour</description>
	<lastBuildDate>Thu, 07 May 2009 20:09:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David</title>
		<link>http://michaeldaw.org/papers/paper-290507/comment-page-1#comment-49547</link>
		<dc:creator>David</dc:creator>
		<pubDate>Thu, 17 Jan 2008 07:14:09 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/papers/paper-290507/#comment-49547</guid>
		<description>ups.. :) now i see that this site is support tag ()
And in my up post i meant code like
[]</description>
		<content:encoded><![CDATA[<p>ups.. :) now i see that this site is support tag ()<br />
And in my up post i meant code like<br />
[]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://michaeldaw.org/papers/paper-290507/comment-page-1#comment-49546</link>
		<dc:creator>David</dc:creator>
		<pubDate>Thu, 17 Jan 2008 07:06:41 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/papers/paper-290507/#comment-49546</guid>
		<description>Hello, guys!
I&#039;m very interesting about this article and especially about XSIO - Cross Site Image Overlaying
But.. I&#039;v tested many socials networks like myspace, digg, etc and couldn&#039;t find such vulns
I mean, that wnen I type in comments a code like:

I don&#039;t see the image in comments.
Could some body explain^ may be this bug already fixed everywhere or what I&#039;m making wrong?

----------
Thank&#039;s beforehand!</description>
		<content:encoded><![CDATA[<p>Hello, guys!<br />
I&#8217;m very interesting about this article and especially about XSIO &#8211; Cross Site Image Overlaying<br />
But.. I&#8217;v tested many socials networks like myspace, digg, etc and couldn&#8217;t find such vulns<br />
I mean, that wnen I type in comments a code like:</p>
<p>I don&#8217;t see the image in comments.<br />
Could some body explain^ may be this bug already fixed everywhere or what I&#8217;m making wrong?</p>
<p>&#8212;&#8212;&#8212;-<br />
Thank&#8217;s beforehand!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kuza55</title>
		<link>http://michaeldaw.org/papers/paper-290507/comment-page-1#comment-35215</link>
		<dc:creator>kuza55</dc:creator>
		<pubDate>Sat, 02 Jun 2007 13:03:08 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/papers/paper-290507/#comment-35215</guid>
		<description>Whoops, my mistake, since you needed to provide a domain initially I assumed (:() that it was tied - I should really start checking all the things I say.

But I would still be surprised if it didn&#039;t raise a flag somewhere at Google when some code starts getting used on a new site.</description>
		<content:encoded><![CDATA[<p>Whoops, my mistake, since you needed to provide a domain initially I assumed (:() that it was tied &#8211; I should really start checking all the things I say.</p>
<p>But I would still be surprised if it didn&#8217;t raise a flag somewhere at Google when some code starts getting used on a new site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ad-Jacking Affiliate Anchor Tags - Operation n</title>
		<link>http://michaeldaw.org/papers/paper-290507/comment-page-1#comment-34907</link>
		<dc:creator>Ad-Jacking Affiliate Anchor Tags - Operation n</dc:creator>
		<pubDate>Sat, 02 Jun 2007 00:16:10 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/papers/paper-290507/#comment-34907</guid>
		<description>[...] This article is part of my concept Ad-Jacking: XSSing for Fun and Profit. [...]</description>
		<content:encoded><![CDATA[<p>[...] This article is part of my concept Ad-Jacking: XSSing for Fun and Profit. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david.kierznowski</title>
		<link>http://michaeldaw.org/papers/paper-290507/comment-page-1#comment-34414</link>
		<dc:creator>david.kierznowski</dc:creator>
		<pubDate>Fri, 01 Jun 2007 01:18:25 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/papers/paper-290507/#comment-34414</guid>
		<description>Kuza55:
Adsense is not domain specific, you can have adsense running on multiple domains, see: http://adsense.blogspot.com/2005/08/from-inside-adsense-mail-bag.html

Obviously nonces don&#039;t help much when XSS is involved, as we can fetch the nonce from the page and then append the appropriate data. In fact, who cares, most affiliate programmes dont support this and adsense data can be replayed successfully, I have tested this. Whats more, part of ad-jacking is adding our own content including nonces (if any) into a page, effectively ad-jacking it.</description>
		<content:encoded><![CDATA[<p>Kuza55:<br />
Adsense is not domain specific, you can have adsense running on multiple domains, see: <a href="http://adsense.blogspot.com/2005/08/from-inside-adsense-mail-bag.html" rel="nofollow">http://adsense.blogspot.com/2005/08/from-inside-adsense-mail-bag.html</a></p>
<p>Obviously nonces don&#8217;t help much when XSS is involved, as we can fetch the nonce from the page and then append the appropriate data. In fact, who cares, most affiliate programmes dont support this and adsense data can be replayed successfully, I have tested this. Whats more, part of ad-jacking is adding our own content including nonces (if any) into a page, effectively ad-jacking it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kuza55</title>
		<link>http://michaeldaw.org/papers/paper-290507/comment-page-1#comment-34399</link>
		<dc:creator>kuza55</dc:creator>
		<pubDate>Fri, 01 Jun 2007 00:40:42 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/papers/paper-290507/#comment-34399</guid>
		<description>Ah, alright, I guess I missed your point then. I thought you were talking about smiulating user actions like ad clicks, but I see what you mean now.

One thing which Google does is tie the Adsense code to a specific domain, so you&#039;d have to either sign up with a different account for every site, or create an iframe to your domain, and have the ad serving code there, so that its rendered on your domain.

But to answer your question; yes it does matter if the ad company is using nonces, because unless we know those nonces we can&#039;t simulate user clicks, and can only either hijack clicks (by placing the iframe under the cursor), or by serving the ads and getting CPM money.</description>
		<content:encoded><![CDATA[<p>Ah, alright, I guess I missed your point then. I thought you were talking about smiulating user actions like ad clicks, but I see what you mean now.</p>
<p>One thing which Google does is tie the Adsense code to a specific domain, so you&#8217;d have to either sign up with a different account for every site, or create an iframe to your domain, and have the ad serving code there, so that its rendered on your domain.</p>
<p>But to answer your question; yes it does matter if the ad company is using nonces, because unless we know those nonces we can&#8217;t simulate user clicks, and can only either hijack clicks (by placing the iframe under the cursor), or by serving the ads and getting CPM money.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david.kierznowski</title>
		<link>http://michaeldaw.org/papers/paper-290507/comment-page-1#comment-33949</link>
		<dc:creator>david.kierznowski</dc:creator>
		<pubDate>Thu, 31 May 2007 07:11:24 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/papers/paper-290507/#comment-33949</guid>
		<description>Mod&#039;ed this comment, it was very sarcastic before :)

Kuza55: well this is exactly the kind of thing I&#039;m currently researching. Let me try answer your questions with a question:
If we have XSS on the current ad serving page do we really care if they are using nonces?

Your comment seems to be driven toward XSSing the Ad Servers.. I am referring more toward an attacker using the XSS vector to spread his/her ad network (i.e. Persistent XSS in forum, reflected XSS in search engine etc) </description>
		<content:encoded><![CDATA[<p>Mod&#8217;ed this comment, it was very sarcastic before :)</p>
<p>Kuza55: well this is exactly the kind of thing I&#8217;m currently researching. Let me try answer your questions with a question:<br />
If we have XSS on the current ad serving page do we really care if they are using nonces?</p>
<p>Your comment seems to be driven toward XSSing the Ad Servers.. I am referring more toward an attacker using the XSS vector to spread his/her ad network (i.e. Persistent XSS in forum, reflected XSS in search engine etc)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kuza55</title>
		<link>http://michaeldaw.org/papers/paper-290507/comment-page-1#comment-33943</link>
		<dc:creator>kuza55</dc:creator>
		<pubDate>Thu, 31 May 2007 06:57:10 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/papers/paper-290507/#comment-33943</guid>
		<description>AFAIK Google and Yahoo (and most likely others) write an iframe to the page, and the iframe contains links with nonces in them, so unless you&#039;re talking about XSS Vulns in the ad serving domain (which is highly unlikely since both Google and Yahoo use domains separate from all their other domains for serving ads), then I&#039;m not quite sure where this is going.

And if you *are* talking about XSS holes in ad serving domains, well, I don&#039;t think that you&#039;re going to find any on an ad serving company of any size, with semi-decent web server configurations.</description>
		<content:encoded><![CDATA[<p>AFAIK Google and Yahoo (and most likely others) write an iframe to the page, and the iframe contains links with nonces in them, so unless you&#8217;re talking about XSS Vulns in the ad serving domain (which is highly unlikely since both Google and Yahoo use domains separate from all their other domains for serving ads), then I&#8217;m not quite sure where this is going.</p>
<p>And if you *are* talking about XSS holes in ad serving domains, well, I don&#8217;t think that you&#8217;re going to find any on an ad serving company of any size, with semi-decent web server configurations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david.kierznowski</title>
		<link>http://michaeldaw.org/papers/paper-290507/comment-page-1#comment-33250</link>
		<dc:creator>david.kierznowski</dc:creator>
		<pubDate>Wed, 30 May 2007 06:42:40 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/papers/paper-290507/#comment-33250</guid>
		<description>ntp, think of it as click-fraud on steroids; the direction of this article is to demonstrate snippets of code that attackers can use with the rising of web 2.0. It is no longer about what an attacker can embed in his page, but what an attacker can embed in others web sites with web 2.0 super-worm, propogating with JSON and XSS. We can manipulate and hijack websites current Ad schemes, rewrite pages etc. Click-fraud is obsolete :)</description>
		<content:encoded><![CDATA[<p>ntp, think of it as click-fraud on steroids; the direction of this article is to demonstrate snippets of code that attackers can use with the rising of web 2.0. It is no longer about what an attacker can embed in his page, but what an attacker can embed in others web sites with web 2.0 super-worm, propogating with JSON and XSS. We can manipulate and hijack websites current Ad schemes, rewrite pages etc. Click-fraud is obsolete :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ntp</title>
		<link>http://michaeldaw.org/papers/paper-290507/comment-page-1#comment-33206</link>
		<dc:creator>ntp</dc:creator>
		<pubDate>Wed, 30 May 2007 02:21:37 +0000</pubDate>
		<guid isPermaLink="false">http://michaeldaw.org/papers/paper-290507/#comment-33206</guid>
		<description>click-fraud?</description>
		<content:encoded><![CDATA[<p>click-fraud?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
