CFPARAM for Simple String Validation
With the addition of a dozen new type values for the cfparam tag in ColdFusion 7, it has become a handy tool for validation.
I have a little trick for those of you who are using earlier versions of ColdFusion that don't support the new types for validation. One of the type attribute values that has been supported for quite some time is the variablename type.
This is handy for validating that a simple one word string has been been passed. According to the docs a varaiblename starts with a letter, underscore (_), or Unicode currency symbol, and contains letters, numbers, underscores, periods, and Unicode currency symbols, only. This means that this type has safety from cross site scripting attacks, and sql injection attacks.
The code may look something like this:
<cfparam name="url.action" type="variablename" default="edit">
If you have ColdFusion 7 you can one up this and limit the values passed in with a simple regular expression:
<cfparam name="url.action" default="edit" type="regex" pattern="(new|edit|delete)">
The regex example only allows the string's new, edit, or delete to be passed in. That's a solid way to validate our input strings.
Wouldn't it be nice however if you could do something like this:
<cfparam name="url.action" type="finite" list="new,edit,delete">
Tweet
add to del.icio.us
| Tags: security, validation, cfparam, strings, xss, sql injection, regex
Related Entries
- Announcing Web Application Firewall for ColdFusion - July 9, 2007
- Web Application Vulnerabilities trump Buffer Overflows - November 2, 2006
- Firefox Aurora now Supports Content Security Policy 1.0 - May 31, 2013
- HackMyCF Scanner Updated - February 1, 2011
- Using AntiSamy with ColdFusion - August 5, 2010
Trackbacks
Comments
Invalid parameter type.
The value cannot be converted to a numeric because it is not a simple value. Simple values are booleans, numbers, strings, and date-time values.
"The value"? Great. Now I know is that one of my numeric form fields threw an error, but not which one... guess I can tell the user to double-check ALL of his entries.
Validate the input client side with Javascript (if enabled), then validate they're not trying to do anything nasty with the data on the back end. Most of this type of error, seems to be from someone trying to do something malicious to the data, rather than someone entering their e-mail address incorrectly.
The alternate is to cftry/cfcatch each item, but of course that's going to create much more time and overhead.
Post a Comment
Recent Entries
- Firefox Aurora now Supports Content Security Policy 1.0
- Writing Secure CFML cfObjective 2013 Slides
- Upgrading to Java 7 on Linux
- J2EE Sessions in CF10 Uses Secure Cookies
- Learn about ColdFusion Security at cfObjective 2013
- Session Loss and Session Fixation in ColdFusion
- FuseGuard 2.3 Released
- CKEditor Spell Checker Plugin





