<?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: Ajax [in]Security</title>
	<atom:link href="http://www.cigital.com/justiceleague/2007/04/02/ajax-insecurity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cigital.com/justiceleague/2007/04/02/ajax-insecurity/</link>
	<description>The Cigital Software Security and Quality Blog</description>
	<lastBuildDate>Fri, 15 Jan 2010 15:00:13 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Romain</title>
		<link>http://www.cigital.com/justiceleague/2007/04/02/ajax-insecurity/comment-page-1/#comment-270</link>
		<dc:creator>Romain</dc:creator>
		<pubDate>Wed, 11 Apr 2007 17:39:25 +0000</pubDate>
		<guid isPermaLink="false">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>
