pf » Detecting SQL Injection with ScriptProtect

Detecting SQL Injection with ScriptProtect

coldfusiondatabases

It occurred to me this morning that ScriptProtect can be a handy feature for globally catching a few forms of SQL Injection Attacks

WARNING - just like its inability to protect against all forms of XSS attacks this solution DOES NOT protect you from all SQL Injection attacks.

You can edit, and add the regular expression patterns for the scriptprotect feature in ColdFusion MX 7 by editing neo-security.xml located in WEB-INF/cfusion/lib. Add the following pattern under the default cross site scripting pattern.

<var name=";.*(select|insert|update|delete|drop|alter|create)">
<string>SQL_INJECTION_ATTEMPT</string>
</var>

I first tried just using a ; as the pattern - but that caused problems with some of the variables in the CGI scope (things like User Agent often have semi-colon's in them). So the pattern now looks for a semi-colon followed by zero or more characters followed by a select, insert, update, delete, drop alter or a create.

Don't expect to catch all possible SQL Injection attacks with this, so don't trust it to stop them. I'm just posting this FYI.



Related Entries
3 people found this page useful, what do you think?

WAF for CF
Trackback Address: 363/A18737366BA3861EE07811CCF05BF201
On 05/19/2005 at 6:32:34 PM MDT Brian G wrote:
1
What happens if this pattern is detected? Does it throw an error you can catch with CFCATCH or just put something in the logs?

On 05/29/2005 at 2:01:57 PM MDT Anonymous wrote:
2
Hmmm strange, because this won't work:

;.*(select|insert|update|delete|drop|alter|create)

If that is used a as a regular expression, then it never even reaches the select, insert, etc etc. Because the . character is acting like a lazy match. Which finds ANYTHIGN beyond the ; character.

On 10/27/2005 at 5:02:31 PM MDT David S wrote:
3
This would be great if it worked. Tried it and it didn't prevent a SQL injection attack. It also caused errors in the CGI scope.

On 08/22/2007 at 8:41:17 AM MDT matt wrote:
4
I used this instead and it worked great.

\s*(select|insert|update|delete|drop|alter|create)

On 08/18/2008 at 5:44:55 PM MDT speqy wrote:
5
also need to test for exec|cast|declare -- to prevent attacks where the SQL code is encoded as a hex string




  



Spell Checker by Foundeo





Subscribe to my RSS Feed: solosub RSS
Tags