<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/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>How to protect yourself against the latest SQL injection</title><link>http://weblogs.asp.net/pleloup/archive/2008/12/20/how-to-protect-yourself-against-the-latest-sql-injection.aspx</link><description>Now it's time to rejoice and be positive. Following my different posts about the latest SQL injection attacks, I got all sort of comments. Roughly half of the commenters saying I am a moron, why you don't go back to school and protect your databases,</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>re: How to protect yourself against the latest SQL injection</title><link>http://weblogs.asp.net/pleloup/archive/2008/12/20/how-to-protect-yourself-against-the-latest-sql-injection.aspx#6800738</link><pubDate>Mon, 22 Dec 2008 13:16:09 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6800738</guid><dc:creator>Jonathan</dc:creator><author>Jonathan</author><description>&lt;p&gt;How exactly are they able to execute the SQL code on your server?&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6800738" width="1" height="1"&gt;</description></item><item><title>re: How to protect yourself against the latest SQL injection</title><link>http://weblogs.asp.net/pleloup/archive/2008/12/20/how-to-protect-yourself-against-the-latest-sql-injection.aspx#6799997</link><pubDate>Sun, 21 Dec 2008 20:37:11 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6799997</guid><dc:creator>pbz</dc:creator><author>pbz</author><description>&lt;p&gt;&lt;em&gt;&amp;quot;I confirm that my code is doing all the checks required on the frontend. Because it&amp;#39;s a cookie exploiting a flaw in IE, the execution of the code is totally transparent, nothing really I can do in my code. However securing the basics of SQL Server like the EXEC rights on the Master table has been successful. Paschal&amp;quot;&lt;/em&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If this a new threat that can bypass all my parameterized queries I&amp;#39;m all ears! If that&amp;#39;s the case &amp;nbsp;a simple proof of concept would be helpful. What you&amp;#39;re doing here, however, is securing SQL Server rather than fixing your application. Don&amp;#39;t get me wrong, nothing wrong in securing your database, but you should fix your application first. If you can prove us that&amp;#39;s fixed and the trojan successfully bypasses your checks please let us know with an example. Thanks.&lt;/p&gt;&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6799997" width="1" height="1"&gt;</description></item><item><title>re: How to protect yourself against the latest SQL injection</title><link>http://weblogs.asp.net/pleloup/archive/2008/12/20/how-to-protect-yourself-against-the-latest-sql-injection.aspx#6799171</link><pubDate>Sat, 20 Dec 2008 14:54:54 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6799171</guid><dc:creator>ca8msm</dc:creator><author>ca8msm</author><description>&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;&amp;quot;Thanks for that info. Yes I am surely stupd because I don&amp;#39;t know all the web config attributes by heart. Come on,&amp;nbsp;be nice ;-)&amp;nbsp; And yes if Microsoft can provide this behavior by default that will save a lot of my time Thanks anyway for the tip! - Paschal&amp;quot;&lt;/em&gt;&amp;nbsp;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&amp;quot;I think that the new threat posed by the trojan recently is that it used a flaw in Internet Explorer to be able to expose a cookie to a request stream and execute some SQL command.&amp;quot;&lt;/p&gt;
&lt;p&gt;It&amp;#39;s not really a flaw, and it&amp;#39;s not just limited to IE. No-one apart from the caller should be able to view your cookies so if they are being sent elsewhere it&amp;#39;s because YOU (not Microsoft) haven&amp;#39;t locked them down successfully. Usually, a form of XSS is used to trick the page into sending the cookie elsewhere so I&amp;#39;d suggest reading up on that first. Here&amp;#39;s our wiki article on the subject:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://wiki.lessthandot.com/index.php/ASP.NET:_How_to_set_cookies_as_httponly" target="_new" rel="nofollow"&gt;wiki.lessthandot.com/.../ASP.NET:_How_to_set_cookies_as_httponly&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I really wish people would take the responsibility of securing their websites themselves rather than looking to blame the web server or the server-side language they use. They provide the tools to serve your site but it&amp;#39;s you who needs to secure it.&lt;/p&gt;&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6799171" width="1" height="1"&gt;</description></item><item><title>How to protect yourself against the latest SQL injection - help.net</title><link>http://weblogs.asp.net/pleloup/archive/2008/12/20/how-to-protect-yourself-against-the-latest-sql-injection.aspx#6799151</link><pubDate>Sat, 20 Dec 2008 14:14:09 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6799151</guid><dc:creator>How to protect yourself against the latest SQL injection - help.net</dc:creator><author>How to protect yourself against the latest SQL injection - help.net</author><description>&lt;p&gt;Pingback from &amp;nbsp;How to protect yourself against the latest SQL injection - help.net&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6799151" width="1" height="1"&gt;</description></item></channel></rss>