<?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: JavaScript Remoting Dangers</title>
	<atom:link href="http://www.gnucitizen.org/blog/javascript-remoting-dangers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gnucitizen.org/blog/javascript-remoting-dangers/</link>
	<description>Information Security Think Tank</description>
	<pubDate>Tue, 06 Jan 2009 04:37:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: James</title>
		<link>http://www.gnucitizen.org/blog/javascript-remoting-dangers/comment-page-1/#comment-122422</link>
		<dc:creator>James</dc:creator>
		<pubDate>Mon, 02 Jun 2008 18:19:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/javascript-remoting-dangers#comment-122422</guid>
		<description>Hello, 

Can you please clarify how this example works:

&lt;pre&gt;&lt;code&gt;var iframe = document.createElement('IFRAME');
//have the IFRAME download the content we want to steal
iframe.src = 'http://site.com/AddressBook.php);
//make the IFRAME invisible
iframe.style="width:0px; height:0px; border: 0px"
//set our function to call when the IFRAME is done loading
iframe.onload = callbackFunction;
//now add the IFRAME to the DOM.
Document.body.appendChild(iframe);&lt;/code&gt;&lt;/pre&gt;

From what I can tell, the above code will only work if this script is included on the site.com domain.  iframes prevent access to their data by parent windows of different domain names.  Therefore, I don't see how an attacker can access this data?  

I use this technique in one of my applications to pass data from one website to another, but I have control of both websites.  I placed a script tag on domainA from domainB.  without access to domainA, I don't see how this can be accomplished.

I hope my question is clear.  Please email me if it's not as I feel it's important that I understand the security implications of this technique for my product.

Thanks,
James</description>
		<content:encoded><![CDATA[<p>Hello, </p>
<p>Can you please clarify how this example works:</p>
<pre><code>var iframe = document.createElement('IFRAME');
//have the IFRAME download the content we want to steal
iframe.src = 'http://site.com/AddressBook.php);
//make the IFRAME invisible
iframe.style="width:0px; height:0px; border: 0px"
//set our function to call when the IFRAME is done loading
iframe.onload = callbackFunction;
//now add the IFRAME to the DOM.
Document.body.appendChild(iframe);</code></pre>
<p>From what I can tell, the above code will only work if this script is included on the site.com domain.  iframes prevent access to their data by parent windows of different domain names.  Therefore, I don&#8217;t see how an attacker can access this data?  </p>
<p>I use this technique in one of my applications to pass data from one website to another, but I have control of both websites.  I placed a script tag on domainA from domainB.  without access to domainA, I don&#8217;t see how this can be accomplished.</p>
<p>I hope my question is clear.  Please email me if it&#8217;s not as I feel it&#8217;s important that I understand the security implications of this technique for my product.</p>
<p>Thanks,<br />
James</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cheat Code &#187; JavaScript Remoting Dangers</title>
		<link>http://www.gnucitizen.org/blog/javascript-remoting-dangers/comment-page-1/#comment-5242</link>
		<dc:creator>Cheat Code &#187; JavaScript Remoting Dangers</dc:creator>
		<pubDate>Sat, 24 Feb 2007 14:38:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/javascript-remoting-dangers#comment-5242</guid>
		<description>[...] Original post by pdp and powered by Img Fly [...]</description>
		<content:encoded><![CDATA[<p>[...] Original post by pdp and powered by Img Fly [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: busin3ss</title>
		<link>http://www.gnucitizen.org/blog/javascript-remoting-dangers/comment-page-1/#comment-3110</link>
		<dc:creator>busin3ss</dc:creator>
		<pubDate>Thu, 01 Feb 2007 06:07:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/javascript-remoting-dangers#comment-3110</guid>
		<description>awesome article... you guys rock! Keep up the good work</description>
		<content:encoded><![CDATA[<p>awesome article&#8230; you guys rock! Keep up the good work</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pdp</title>
		<link>http://www.gnucitizen.org/blog/javascript-remoting-dangers/comment-page-1/#comment-3061</link>
		<dc:creator>pdp</dc:creator>
		<pubDate>Wed, 31 Jan 2007 09:28:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/javascript-remoting-dangers#comment-3061</guid>
		<description>very interesting summary. good stuff.</description>
		<content:encoded><![CDATA[<p>very interesting summary. good stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pagvac</title>
		<link>http://www.gnucitizen.org/blog/javascript-remoting-dangers/comment-page-1/#comment-3033</link>
		<dc:creator>pagvac</dc:creator>
		<pubDate>Tue, 30 Jan 2007 22:56:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/javascript-remoting-dangers#comment-3033</guid>
		<description>Nice job Acidus! This is a very nice summary of different ways to craft nasty HTTP requests using JavaScript.</description>
		<content:encoded><![CDATA[<p>Nice job Acidus! This is a very nice summary of different ways to craft nasty HTTP requests using JavaScript.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
