<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:cc="http://web.resource.org/cc/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">

			<channel>
			<title>ColdFusion Muse - Coldfusion Security</title>
			<link>http://www.coldfusionmuse.com/index.cfm</link>
			<description>Musings and Other Things from CF Guru Mark Kruger</description>
			<language>en-us</language>
			<pubDate>Thu, 02 Sep 2010 20:15:37 -0500</pubDate>
			<lastBuildDate>Fri, 16 Apr 2010 14:11:00 -0500</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>mkruger@cfwebtools.com</managingEditor>
			<webMaster>mkruger@cfwebtools.com</webMaster>
			<itunes:subtitle></itunes:subtitle>
			<itunes:summary></itunes:summary>
			<itunes:category text="Technology" />
			<itunes:category text="Technology">
				<itunes:category text="Podcasting" />
			</itunes:category>
			<itunes:category text="Technology">
				<itunes:category text="Tech News" />
			</itunes:category>
			<itunes:keywords></itunes:keywords>
			<itunes:author></itunes:author>
			<itunes:owner>
				<itunes:email>mkruger@cfwebtools.com</itunes:email>
				<itunes:name></itunes:name>
			</itunes:owner>
			<itunes:image href="" />
			<image>
				<url></url>
				<title>ColdFusion Muse</title>
				<link>http://www.coldfusionmuse.com/index.cfm</link>
			</image>
			<itunes:explicit>no</itunes:explicit>
			
			
			
			
			
			<item>
				<title>Another SQLi Attack: Urchin.js</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2010/4/16/SQLi-char-urchin</link>
				<description>
				
				&lt;p&gt;
	I spent yesterday cleaning and inoculating another server infected with SQL Injection. Unless you have been living in a cave you know that SQL injection (SQLi) is the most common vulnerability of web based application. This is due to 2 factors - 1) almost all databases use numeric fields and B) web applications by nature pass user input into queries. Of course I could throw in there that web developers are often lax about inoculating their code. There is also the problem of legacy code - code that has been around since the dark ages of the late 90&apos;s. Of course SQLi has been around that long as well, but it is surprising how much legacy code chugs along for a decade or more with no problem in spite of the vulnerability.
&lt;/p&gt;
&lt;p&gt;
	Anyway, here&apos;s the skinny on the latest attack I found. It uses our old friend &quot;Cast&quot; in conjunction with the char() function of MS SQL. Note, this is not a new attack on the web - it&apos;s only new to me in that I&apos;ve never battled this particular attack before.
&lt;/p&gt;
				 [More]
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<category>ColdFusion</category>				
				
				<pubDate>Fri, 16 Apr 2010 14:11:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2010/4/16/SQLi-char-urchin</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>Script Injection: File Upload Using a Subdomain</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2009/9/21/script.injection.solutions</link>
				<description>
				
				&lt;p&gt;
	If you read my post on the &lt;a href=&quot;http://www.coldfusionmuse.com/index.cfm/2009/9/18/script.insertion.attack.vector&quot;&gt;script injection attack&lt;/a&gt; that has been going around you will note that I suggest four solutions or remedies to protect your server (upload off the web root, use cfcontent, disable script and execute permissions on certain directories, and remove superfluous handlers). A fifth solution was pointed out to me that is somewhat related to uploading off of the web root.
&lt;/p&gt;
&lt;p&gt;
	The idea would be to create a subdomain just for user resources. So, for example, you could have &quot;www.ilovemoles.com&quot; and &quot;pics.ilovemoles.com&quot;.  User uploads would go the share for the &quot;pics&quot; subdomain and be served from there.  You would still vet the content to make sure it was ok, but the &quot;pics&quot; domain would not allow ColdFusion (or PHP or ASP or any scripts or executable at all). I can see some issues that you might run into - chiefly that you are not really &quot;securing&quot; the content from unauthorized access. I believe that still makes it suitable for public resources, but not able to be fully integrated into an application without a lot of run around. Still it seems an elegant solution.
&lt;/p&gt;
				
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<pubDate>Mon, 21 Sep 2009 10:12:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2009/9/21/script.injection.solutions</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>Script Injection Attack: Smoking Gun?</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2009/9/18/script.insertion.attack.vector</link>
				<description>
				
				&lt;p&gt;
	Many of you may know there is a web server attack going on in the wild that involves appending a JS script to all the htm, php, cfm, js, jsp files found on a server. If you are unfamiliar with this attack see some of my previous posts like &lt;a href=&quot;http://www.coldfusionmuse.com/index.cfm/2009/4/16/iframe.insertion.hack&quot;&gt;this one&lt;/a&gt; for more of an explanation. While I have found the script that actually does this dirty deed and I have combated this issue on numerous servers by now, I have never really been confident that I have discovered where the attack actually begins (i.e. how this file gets on the server to begin with). Yesterday I was made aware of a technique that &lt;em&gt;might&lt;/em&gt; be the smoking gun. It has been tested by some folks I trust and I want to give a full explanation here to assist all those Muse readers who battle the bad guys at the server level. 
&lt;/p&gt;
&lt;p&gt;If you are a technician or network operations professional who is trying to scan your way out of this attack, I&apos;m afraid you are probably out of luck (but keep reading anyway). This attack specifically targets application code - not just CF but ASP, JSP, PHP and any others. All of them can be subject to this problem because it has to do with insecure coding, not specific platform vulnerabilities. I would add that if you find your code vulnerable don&apos;t feel too bad. This exploit is clever enough to get by code that &lt;em&gt;seems secure&lt;/em&gt; as we shall see. If you are a web developer of any stripe you should &lt;strong&gt;definitely read this post&lt;/strong&gt;. The examples are in ColdFusion, but you will be able to extrapolate for your own language or technology pretty easily.
&lt;/p&gt;
				 [More]
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<pubDate>Fri, 18 Sep 2009 13:07:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2009/9/18/script.insertion.attack.vector</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>My Funny Val()entine and SQLi</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2009/6/15/coldfusion.val.sqli</link>
				<description>
				
				&lt;p&gt;
	Regular readers know I&apos;m always on the lookout for interesting issues regarding SQL Injection and ColdFusion. This year has been a banner year for injection on ColdFusion sites and if you are not on the Cfqueryparam bandwagon yet I have one more example of a code that might &lt;em&gt;seem&lt;/em&gt; to be inoculated but is not. It has to do with the use of val( )....
&lt;/p&gt;
				 [More]
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<category>ColdFusion</category>				
				
				<pubDate>Mon, 15 Jun 2009 14:30:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2009/6/15/coldfusion.val.sqli</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>Cfinclude for Good or Evil</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2009/5/14/cfinclude.arbitrary.file.extensions</link>
				<description>
				
				&lt;p&gt;
	Yesterday I was doing some searches on a sick server to troubleshoot the &lt;a href=&quot;http://www.coldfusionmuse.com/index.cfm/2009/4/23/Iframe.VBscript&quot;&gt;Iframe Injection&lt;/a&gt; issue. A user had posted some additional information regarding a file that appeared on his server that had this issue. The file was named &quot;fection.cfm&quot; so we now know the hacker casually removes his prefixes (or I should say &apos;emoves his &apos;efixes). I began my search by looking for the file specifically, then moved on to look for the string &quot;cfexecute&quot; in all of the *.cfm files. But that got me thinking. A clever hacker might know some things about ColdFusion. He could in fact, further obscure his code with some knowledge of cfinclude and IIS. Such a technique can be used to secure your code as well. You can create code that is only runnable by ColdFusion using cfinclude. Here&apos;s the skinny.
&lt;/p&gt;
				 [More]
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<category>ColdFusion</category>				
				
				<pubDate>Thu, 14 May 2009 11:23:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2009/5/14/cfinclude.arbitrary.file.extensions</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>ISAPIRewrite or Mod_Rewrite Rules</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2008/8/8/isapi-rewrite-rule-prevents-sql-injection</link>
				<description>
				
				&lt;p&gt;
For those of you interested in stopping the SQLi attack before it even hits your ColdFusion server, you might try these rewrite rules are from the CF-Linux email list (run by &lt;a href=&quot;http://www.houseoffusion.com&quot;&gt;House of Fusion&lt;/a&gt;). They were provided by list member Mike Chytracek and forwarded to me by Linux CFG &lt;a href=&quot;http://www.stillnetstudios.com/&quot;&gt;Ryan Stille&lt;/a&gt;.
These rules are for for use with Helicon&apos;s ISAPI Rewrite filter, but with very little tweaking these rules aught to work for Apache Mod_rewrite as well.

&lt;pre font-family: courier new; font-size: 10pt;&gt;
&lt;br&gt;
# Helicon ISAPI_Rewrite configuration file&lt;br&gt;
# Version 3.1.0.54&lt;br&gt;

RewriteEngine On&lt;br&gt;
RewriteCompatibility2 On&lt;br&gt;
RepeatLimit 20&lt;br&gt;
RewriteBase &lt;br&gt;
# unsupported directive: [ISAPI_Rewrite]&lt;br&gt;

# CacheClockRate 300&lt;br&gt;

RewriteRule ^.*DECLARE%20.*$ http://www.cybercrime.gov/ [NC]&lt;br&gt;
RewriteRule ^.*NVARCHAR.*$ http://www.cybercrime.gov/ [NC]&lt;br&gt;
RewriteRule ^.*sp_password.*$ http://www.cybercrime.gov/ &lt;br&gt;[NC]
RewriteRule ^.*%20xp_.*$ http://www.cybercrime.gov/ [NC]&lt;br&gt;
RewriteRule ^.*EXEC\(@.*$ http://www.cybercrime.gov/ [NC]&lt;br&gt;
RewriteRule ^.*%20@.*$ http://www.cybercrime.gov/ [NC]&lt;br&gt;

RewriteRule ^METHOD$ OPTIONS&lt;br&gt;
&lt;/pre&gt;
&lt;/p&gt;
&lt;p&gt;
Please note that these rules will actually redirect the request to the governments cybercrime website. That&apos;s going to freak a few folks out if you end up with any fals positives :)
&lt;/p&gt;
				
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<pubDate>Fri, 08 Aug 2008 16:29:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2008/8/8/isapi-rewrite-rule-prevents-sql-injection</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>SQLi Attack on the Rise (Film at 11:00)</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2008/8/8/SQLi-Update-Ben-Speaks-His-Mind</link>
				<description>
				
				&lt;p&gt;
   Unless you have had your head in the sand (those of you on your honeymoon are excused) you know that the ColdFusion world has been awash in SQL Injection attacks over the last month. Anecdotally I am seeing a significant increase in attacks this week - about 15 times what they were a few days ago. Michael Dinowitz reports that house of fusion was receiving 4000 attacks in 5 minutes (that&apos;s nearly 50 thousand an hour).  &lt;a href=&quot;http://www.codersrevolution.com/&quot;&gt;Brad Wood&lt;/a&gt; reports no less 90 request per second. The suspicion is that the attack is driven by searching Google for sites with &quot;.cfm&quot; pages. That means the more successful that you are at search engine optimization the more likely you are to be targeted. Conversely if you don&apos;t have a good number of pages ranked then you are probably then you will see fewer attacks. 
&lt;/p&gt;
&lt;p&gt;
It seems these attacks are orchestrated using infected computers throughout the internet. Some effort is underway to collect IP addresses to see if a pattern emerges. I suspect that approach will not yield fruit, but I still applaud the effort. We (&lt;a href=&quot;http://www.cfwebtools.com&quot;&gt;CF Webtools&lt;/a&gt;) are continuing to assist customers in any way we can - everything from wholesale changes to sites, to blacklist techniques to friendly advice over the phone. As these attacks accelerate they become more like Denial of Service attacks than anything else.  Even if you are binding all your variables and you have great controls you will still have to deal with a bombardment of thousands of requests against your CF pages. I recommend that you use one of the many blacklist techniques out there - at least temporarily. Some folks have started out sending emails alerts when these attacks are underway but quickly discovered that the volume of email can be pretty hefty. I recommend just killing the request - abort it at the top of your application prior to the application being instantiated. Then at least you have kept it from filling up your error log. Meanwhile this round of attacks has had the positive affect of causing folks to suddenly pay attention to a great deal of vulnerable code. Here&apos;s another silver lining you may not have considered...
&lt;/p&gt;
				 [More]
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<pubDate>Fri, 08 Aug 2008 13:30:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2008/8/8/SQLi-Update-Ben-Speaks-His-Mind</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>Ask-a-Muse: How Can Cfqueryparam Protect Me?</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2008/7/28/cfqueryparam-protects-against-daleks</link>
				<description>
				
				&lt;div style=&quot;margin-left: 20px; border-left: 3px solid #CCCCCC; padding-left: 4px;&quot;&gt;
&lt;p&gt;&lt;em&gt;Muse Reader Asks:&lt;/em&gt;&lt;br&gt;	
If you want to allow someone to search your site by keyword, how do you protect against an SQL injection? CFqueryParam is great if testing for an integer, but what about for a string? Surely there&apos;s got to be a way to do it since all kinds of sites let you perform keyword searches. Thanks!
&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;padding-top: 15px;&quot;&gt;
Whoa... slow down there. Do my ears deceive me? Did my reader just indicate that he (or she) thinks that cfqueryparam &quot;tests&quot; for a string? I hate to break it to you, but the purpose of Cfqueryparam is &lt;em&gt;not&lt;/em&gt; to insure that the value passed into the tag is one thing or another. The validation that occurs is more of a by-product of binding. Sure, the tag will error out when you try to pass &quot;abc&quot; instead of &quot;123&quot; to a param of the &quot;integer&quot; type, but that is a result of type binding. It&apos;s simply trying to bind variables of type for the driver to use, so naturally it errors out. But pass in a decimal like 123.123 and it says &quot;okey dokey - that will work&quot;. Testing to see what a form element contains is the job of the developer, not the job of a magic box tag. 
&lt;/p&gt;
&lt;p&gt;
	But to answer your question more specifically, cfqueryparam will protect you from those malicious hack attempts anyway - even if the attack is &lt;em&gt;passed to the database&lt;/em&gt;. Let&apos;s examine a working case and see if we can figure out what is happening.
&lt;/p&gt;
				 [More]
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<pubDate>Mon, 28 Jul 2008 19:19:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2008/7/28/cfqueryparam-protects-against-daleks</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>A Better Blacklist Function for SQLi</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2008/7/28/Coldfusion-Blacklist-Function-for-SQLi</link>
				<description>
				
				&lt;p&gt;
	Please note - I have not changed my stance on the use of CFQUERYPARAM. The real &quot;fix&quot; for injection is validation routines for form inputs and binding variables using Cfqueryparam. A blacklist function (a function that checks for &quot;known bad&quot; input) is useful in that it provides protection on the perimeter. It can help you intercept hack attempts before they reach your DB - where presumably they would fail in any case. They are also useful for thwarting immediate threats if you discover a security flaw that might take some time to fix. The recent spate of attacks caused a proliferation of blacklist techniques from simple to complex. In my own post on the vulnerability of using &lt;a href=&quot;http://www.coldfusionmuse.com/index.cfm/2008/7/21/query-string-with-cfqueryparam&quot;&gt;string concatenated SQL&lt;/a&gt; I published a snippet that made use of the iSQLInject function from &lt;a href=&quot;http://www.cflib.org&quot;&gt;CF Lib&lt;/a&gt;. There is a better approach however.
&lt;/p&gt;
				 [More]
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<pubDate>Mon, 28 Jul 2008 10:29:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2008/7/28/Coldfusion-Blacklist-Function-for-SQLi</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>Adding Cfqueryparams to a Legacy Site Without Losing Your Hair</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2008/7/26/cfqueryparam-tips-for-adding</link>
				<description>
				
				&lt;p&gt;
	So you got hit with the latest SQLi attack eh? SQLi is the hip acronym for &quot;sql injection&quot; that fancy pants security people use. You&apos;ve put in some stop gap measures and now you are slogging through 3000 queries trying to add cfqueryparam to everything. It&apos;s a laborious task to be sure. Here are some special tips from the muse that might help shorten it.
&lt;/p&gt;
				 [More]
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<category>Coldfusion Tips and Techniques</category>				
				
				<pubDate>Sat, 26 Jul 2008 14:28:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2008/7/26/cfqueryparam-tips-for-adding</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>SQL Injection Part III - Don&apos;t Forget Sorting</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2008/7/21/SQL-injection-using-order-by</link>
				<description>
				
				&lt;p&gt;
So... you have diligently added CFQUERYPARAM to every input variable. Your database is secure and safe from SQL Injection - right? Well... maybe not. Did you remember to account for the ORDER BY Clause? Let me explain.
&lt;/p&gt;
				 [More]
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<pubDate>Mon, 21 Jul 2008 12:53:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2008/7/21/SQL-injection-using-order-by</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>Combining SQL Query Strings and CFQUERYPARAM</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2008/7/21/query-string-with-cfqueryparam</link>
				<description>
				
				&lt;p&gt;
	If you have been following the muse the last few days you will know that I&apos;ve had my shoulder to the wheel helping customers and fellow developers sort through making changes to their site to protect against a particularly malicious SQL Injection attack (read about the details &lt;a href=&quot;http://www.coldfusionmuse.com/index.cfm/2008/7/18/Injection-Using-CAST-And-ASCII&quot;&gt;here&lt;/a&gt;). Some of the folks who have contacted me are dealing with extra problems because their code uses string concatenation to build dynamic SQL strings. So the question has been asked a few times, &lt;em&gt;&quot;How do I go about building an SQL string with CFQUERYPARAMs in it?&quot;&lt;/em&gt; Unfortunately, if you have chosen this approach it&apos;s going to be difficult to help you without seriously refactoring your code. Here&apos;s a few tips that can help, and one approach that &lt;em&gt;might&lt;/em&gt; get you most of the way there.
&lt;/p&gt;
				 [More]
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<pubDate>Mon, 21 Jul 2008 00:31:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2008/7/21/query-string-with-cfqueryparam</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>SQL Injection Part II (Make Sure You Are Sitting Down)</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2008/7/18/Injection-Using-CAST-And-ASCII</link>
				<description>
				
				&lt;p&gt;
	Back in February I wrote a blog post on SQL Injection that included an example of how a malicious user might inject into a character field even though ColdFusion escapes single quote marks. The attack involved &lt;em&gt;other&lt;/em&gt; forms of escaping single quotes - and was effective against MySQL. This week I stumbled upon (more like a train wreck) an attack that is much more sophisticated - and also involves injection into a character field. I am told that others have discovered and written on this attack over the last few weeks - but I was unaware of it until a customer of ours was victimized. Amazingly, the specific real world attack I discovered and fixed allowed the hacker to append a string to &lt;em&gt;every char column in every table of the database&lt;/em&gt;. It was so pervasive it left me wondering if it was SQL injection at all - until I found a URL entry that looked something like this:
&lt;/p&gt;
				 [More]
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<pubDate>Fri, 18 Jul 2008 15:52:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2008/7/18/Injection-Using-CAST-And-ASCII</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>Webmaniacs - Cryptography and Dentistry</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2008/5/23/cryptography</link>
				<description>
				
				&lt;p&gt;
        On Tuesday I took in a workshop on Cryptography by &lt;a href=&quot;http://www.fullfrontalnerdity.com/&quot;&gt;Dean Saxe&lt;/a&gt;. Dean is an impressive character with a head stuffed full of knowledge and spilling out everywhere. He obviously knew what he was talking about. As a topic, cryptography is so impossibly complicated and intricate that he could not do it justice in a 50 minute session. Most discussions about cryptography center around keys, algorithms and best practices - and this was no exception. Dean recommended against relying on CF&apos;s own encrypt and decrypt functions for anything but the most rudimentary encryption. In fact, he probably didn&apos;t even go that far. That tidbit of advice is common from almost every security pro I have ever heard mention the subject. When it came to discussing keys it was like a trip to the dentist.
&lt;/p&gt;
				 [More]
				</description>
						
				
				<category>Conferences</category>				
				
				<category>Coldfusion Security</category>				
				
				<pubDate>Fri, 23 May 2008 13:20:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2008/5/23/cryptography</guid>
				
				
			</item>
			
		 	
			
			
			<item>
				<title>Disabling Backslash Escaping in MySQL</title>
				<link>http://www.coldfusionmuse.com/index.cfm/2008/5/16/disable-backslash-escape-on-mysql</link>
				<description>
				
				&lt;p&gt;
For muse readers who read my &lt;a href=&quot;http://www.coldfusionmuse.com/index.cfm/2008/2/22/sql-injection-on-a-character-field&quot;&gt;previous post&lt;/a&gt; on SQL injection examples that use character rather than numeric fields, I offer this tip I picked up on CF-Talk from Azadi Saryev. It appears you can &lt;em&gt;disable&lt;/em&gt; the ability to escape special characters using the backslash. Here is the exact note from Azadi.&lt;/p&gt;
&lt;p&gt;
				 [More]
				</description>
						
				
				<category>Coldfusion Security</category>				
				
				<pubDate>Fri, 16 May 2008 09:31:00 -0500</pubDate>
				<guid>http://www.coldfusionmuse.com/index.cfm/2008/5/16/disable-backslash-escape-on-mysql</guid>
				
				
			</item>
			
		 	
			</channel></rss>