> 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. > 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. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:192601 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
