<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SQL Injection Attacks and Data Thief</title><link>http://blogs.msdn.com/mswanson/archive/2005/01/05/347151.aspx</link><description>Although I wouldn't consider myself a SQL Server expert, like any good developer, I know my way around stored procedures, database normalization, and proper indexing techniques. Occasionally, I get questions from customers about SQL injection attacks.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: SQL Injection Attacks and Data Thief</title><link>http://blogs.msdn.com/mswanson/archive/2005/01/05/347151.aspx#347339</link><pubDate>Thu, 06 Jan 2005 03:43:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:347339</guid><dc:creator>Peter Blum</dc:creator><description>Last year, when Microsoft's ASP.NET Roadshow and DevDays visited Boston, the speakers enphasized SQL Injection and Cross-site scripting attacks. (We're talking about hours on the topic.) With such a large audience and a traveling event like these, I would have thought it inspired the masses.&lt;br&gt;As the author of Professional Validation And More, a replacement to the Microsoft validators, I thought I'd participate by building new Validator controls and tools that reflected the issues mentioned not only by Microsoft but by the same articles you point out.&lt;br&gt;While my &amp;quot;Visual Input Security&amp;quot; has been out since September, it has been met with very little interest, even after last month's 5 star 3 page review in aspNetPRO magazine from Don Kiely. Even from my large Professional Validation And More user base who are very enthusiastic of my work.&lt;br&gt;It tells me that people are ignoring the issue, hoping it will go away, and when they address it, they take the simplest solution, such as stripping out the single quote character. As I learned from reading those articles, there is so much more to input security. Users will protect their textboxes but not their cookies, querystring parameters and hidden fields. Any hole in the page will be tracked down by the hacker, who enjoys these challenges.&lt;br&gt;My own solution was to build a report that runs after the page is generated, showing all of the inputs used and the exact validation and neutralization applied to each. It gives each a rating for security with SQL and Script injection.&lt;br&gt;It doesn't matter whether people buy my software. It DOES matter that they are doing the right thing to protect themselves. So Michael, thanks for speaking up about this.</description></item><item><title>re: SQL Injection Attacks and Data Thief</title><link>http://blogs.msdn.com/mswanson/archive/2005/01/05/347151.aspx#348172</link><pubDate>Fri, 07 Jan 2005 06:53:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:348172</guid><dc:creator>Jon Galloway</dc:creator><description>SQL Injection isn't just about stealing data, either. Here's a story I heard about where a trigger was added to cause an outage in an order processing system: &lt;a target="_new" href="http://weblogs.asp.net/jgalloway/archive/2004/05/05/126958.aspx"&gt;http://weblogs.asp.net/jgalloway/archive/2004/05/05/126958.aspx&lt;/a&gt;&lt;br&gt;&lt;br&gt;Peter - I'm trying to sell you VIS package to my boss. Managers usually like to view this as &amp;quot;that danged single quote thing&amp;quot;; I'm lucky to have a boss who knows better.</description></item><item><title>SQL Injection Attacks and Data Thief</title><link>http://blogs.msdn.com/mswanson/archive/2005/01/05/347151.aspx#360706</link><pubDate>Wed, 26 Jan 2005 12:55:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:360706</guid><dc:creator>システム管理な雑記 -- Sleeve notes of a sysadmin -- Kenji Y</dc:creator><description>SQL Injection Attacks and Data Thief</description></item><item><title>re: SQL Injection Attacks and Data Thief</title><link>http://blogs.msdn.com/mswanson/archive/2005/01/05/347151.aspx#8331374</link><pubDate>Sat, 22 Mar 2008 20:26:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8331374</guid><dc:creator>Mark Kent</dc:creator><description>&lt;P&gt;Hi Mike,&lt;/P&gt;
&lt;P&gt;I work as System Engineer in a major ISP company and we are hosting a large number of legacy ASP applications which contain SQL Injection flaws. I always suggest clients to solve the problem by hardening the source code, but 9 out 10 times they don't have the resources. I have been using this tool when clients agree:&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.codeplex.com/IIS6SQLInjection" target=_new rel=nofollow&gt;http://www.codeplex.com/IIS6SQLInjection&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;So far it seems to be working and I have not had problems except that I cannot install in Windows 64 bit. Have you heard about this tool? Is there a way to make it work in 64 bit? The source code is there but I am not good in C++.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;P.S.: I am not using my real name to avoid problem with my clients.&lt;/P&gt;</description></item><item><title>SQL Express 2005, conviene? - Pagina 2 | hilpers</title><link>http://blogs.msdn.com/mswanson/archive/2005/01/05/347151.aspx#9372206</link><pubDate>Fri, 23 Jan 2009 09:07:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9372206</guid><dc:creator>SQL Express 2005, conviene? - Pagina 2 | hilpers</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.hilpers.it/2532861-sql-express-2005-conviene/2"&gt;http://www.hilpers.it/2532861-sql-express-2005-conviene/2&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>