<?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: Preventing XSS (Cross-Site Scripting) Attacks in ColdFusion</title>
	<atom:link href="http://www.thedevshack.com/preventing-xss-cross-site-scripting-attacks-in-coldfusion/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thedevshack.com/preventing-xss-cross-site-scripting-attacks-in-coldfusion/</link>
	<description>Technology and Programming Blog</description>
	<lastBuildDate>Fri, 16 Dec 2011 16:12:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Sandro</title>
		<link>http://www.thedevshack.com/preventing-xss-cross-site-scripting-attacks-in-coldfusion/#comment-107</link>
		<dc:creator>Sandro</dc:creator>
		<pubDate>Mon, 26 Jul 2010 12:48:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedevshack.com/?p=161#comment-107</guid>
		<description>Hi - 

thanks for the article. It&#039;s great to see such articles targeted at solutions for developers!

Regarding number 4: The sure fire way to prevent this type of attack is to simply search and replace any maliciuous data. In other words, replace script tags, etc… with nothing.
....

It is not &quot;sure fire&quot;. The suggestion to use blacklists usually leads to bad security solutions. Blacklists tend to be bypassable especially when custom-built. They are also tricky to get right. There are a number of arguments that explain why this is a bad idea. Google is a good starting point :-) The xss cheatsheet will give you clear examples of why this is a bad idea.

For most cases, encoding html is a much better solution. So I vote for point number 3 over 4. 

- sandro</description>
		<content:encoded><![CDATA[<p>Hi &#8211; </p>
<p>thanks for the article. It&#8217;s great to see such articles targeted at solutions for developers!</p>
<p>Regarding number 4: The sure fire way to prevent this type of attack is to simply search and replace any maliciuous data. In other words, replace script tags, etc… with nothing.<br />
&#8230;.</p>
<p>It is not &#8220;sure fire&#8221;. The suggestion to use blacklists usually leads to bad security solutions. Blacklists tend to be bypassable especially when custom-built. They are also tricky to get right. There are a number of arguments that explain why this is a bad idea. Google is a good starting point <img src='http://www.thedevshack.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  The xss cheatsheet will give you clear examples of why this is a bad idea.</p>
<p>For most cases, encoding html is a much better solution. So I vote for point number 3 over 4. </p>
<p>- sandro</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PukMype</title>
		<link>http://www.thedevshack.com/preventing-xss-cross-site-scripting-attacks-in-coldfusion/#comment-106</link>
		<dc:creator>PukMype</dc:creator>
		<pubDate>Mon, 03 May 2010 13:15:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedevshack.com/?p=161#comment-106</guid>
		<description>Nikscymn say: I consider, that you are not right. Let&#039;s discuss it. Write to me in PM, we will communicate.
 
_____________
&lt;a href=&quot;http://livitra.rx-tadacip.info/site_map.html&quot; rel=&quot;nofollow&quot;&gt;livitra
 attorneys
  7&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Nikscymn say: I consider, that you are not right. Let&#8217;s discuss it. Write to me in PM, we will communicate.</p>
<p>_____________<br />
<a href="http://livitra.rx-tadacip.info/site_map.html" rel="nofollow">livitra<br />
 attorneys<br />
  7</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: complyordie</title>
		<link>http://www.thedevshack.com/preventing-xss-cross-site-scripting-attacks-in-coldfusion/#comment-105</link>
		<dc:creator>complyordie</dc:creator>
		<pubDate>Tue, 14 Apr 2009 14:51:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedevshack.com/?p=161#comment-105</guid>
		<description>It&#039;s also worth remembering that IE6 will execute javascript: URI&#039;s in the src of an IMG tag.</description>
		<content:encoded><![CDATA[<p>It&#8217;s also worth remembering that IE6 will execute javascript: URI&#8217;s in the src of an IMG tag.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RyanTJ</title>
		<link>http://www.thedevshack.com/preventing-xss-cross-site-scripting-attacks-in-coldfusion/#comment-104</link>
		<dc:creator>RyanTJ</dc:creator>
		<pubDate>Tue, 14 Apr 2009 12:59:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedevshack.com/?p=161#comment-104</guid>
		<description>One set of variables people tend to forget about cleaning are cgi variables. cgi.script_name, cgi.query_string, etc.. 
Keep in mind also that its not just fields a user can enter text in, any field, including hidden, submit buttons, drop downs can be tampered with. FireFox has a plugin called Tamper that is nice to see just what can be tampered with.</description>
		<content:encoded><![CDATA[<p>One set of variables people tend to forget about cleaning are cgi variables. cgi.script_name, cgi.query_string, etc..<br />
Keep in mind also that its not just fields a user can enter text in, any field, including hidden, submit buttons, drop downs can be tampered with. FireFox has a plugin called Tamper that is nice to see just what can be tampered with.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

