<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Ajax [in]Security</title>
	<link>http://www.cigital.com/justiceleague/2007/04/02/ajax-insecurity/</link>
	<description>The Cigital Software Security and Quality Blog</description>
	<pubDate>Thu, 24 Jul 2008 01:34:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: Romain</title>
		<link>http://www.cigital.com/justiceleague/2007/04/02/ajax-insecurity/#comment-270</link>
		<pubDate>Wed, 11 Apr 2007 17:39:25 +0000</pubDate>
		<guid>http://www.cigital.com/justiceleague/2007/04/02/ajax-insecurity/#comment-270</guid>
					<description>I would say that there is no real way to prevent prototype hijacking if you can have a XSS vulnerability in your application.
Btw, prototype hijacking is quite okay to prevent, with basically no remote script inclusion, but the worse is coming with JavaScript 2 operator overloading... With that feature people would be able to totally change the meaning of your script.</description>
		<content:encoded><![CDATA[<p>I would say that there is no real way to prevent prototype hijacking if you can have a XSS vulnerability in your application.<br />
Btw, prototype hijacking is quite okay to prevent, with basically no remote script inclusion, but the worse is coming with JavaScript 2 operator overloading&#8230; With that feature people would be able to totally change the meaning of your script.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
