> Because the query may be called with the cachedwithin attribute which
> doesn't play nice with queryparams. I haven't seen a easy work around
> for this issue yet.
You can cache your query within the Session, Application or Server scopes,
or you might be able to cache a query of that query using
CACHEDWITHIN/CACHEDAFTER.
>> The cache a query of that query using CACHEDWITHIN, I have tried
this but ran into casting issues. MX would make the wrong guess at the data
type of the column.
> But if im not mistaken(easily could be) someone might not need to be
> able to stuff in single quotes to tamper? I think they need the semi
> colon and parens to insert a sub query to blow something up
>
> ;(drop table users) or something of the sort?
There are all sorts of things you might do within an SQL injection attack,
some of which are database-specific. For example, on MS SQL Server, you
might try to open a shell using xp_cmdshell.
>> would the statement made by rick still hold true though. The
attack would need to be able to close the single quotes to embed an attack.
B/C cf escapes them then the embedded sql would always occur inside 'quotes'
thus not being executed but interpreted literally.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting hours spent on a project or with a
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:192613
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54