<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Anatomy of a SQL Injection Incident, Part 2: Meat</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx</link><description>Intro It would appear that the incident I wrote about yesterday is still ongoing. I've been using a search engine to query for the *.js file that's being injected and it looks something like this: Wednesday: 10K hits (This is Avert's number. I didn't</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Se prémunir des attaques de type "SQL Injection"...</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3014910</link><pubDate>Wed, 19 Mar 2008 11:35:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3014910</guid><dc:creator>SQL Server, BizTalk Server, le 64 bits et au-delà !...</dc:creator><description>&lt;p&gt;Pour mieux comprendre les risques auxquels sont expos&amp;amp;#233;es vos bases de donn&amp;amp;#233;es, il est int&amp;amp;#233;ressant&lt;/p&gt;
</description></item><item><title>re: Anatomy of a SQL Injection Incident, Part 2: Meat</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3016741</link><pubDate>Thu, 20 Mar 2008 23:29:17 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3016741</guid><dc:creator>GrumpySecurityGuy</dc:creator><description>&lt;p&gt;Neil is archive.asp part of some standard web software package or are you just using that as an example?&lt;/p&gt;</description></item><item><title>re: Anatomy of a SQL Injection Incident, Part 2: Meat</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3016781</link><pubDate>Fri, 21 Mar 2008 00:44:04 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3016781</guid><dc:creator>neilcar</dc:creator><description>&lt;p&gt;Archive.asp was just an example. &amp;nbsp;The pages involved were all different and didn't appear to have any common code.&lt;/p&gt;
</description></item><item><title>re: Anatomy of a SQL Injection Incident, Part 2: Meat</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3016802</link><pubDate>Fri, 21 Mar 2008 01:12:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3016802</guid><dc:creator>GrumpySecurityGuy</dc:creator><description>&lt;p&gt;Wow that is interesting. So they code is either google dorking for classic ASP pages or performing web crawling itself then? That is pretty scary. I think this is the first example of a widespread defacement that did not use a vulnerability in a known package, like PHPBB etc... Does that sound correct?&lt;/p&gt;</description></item><item><title>re: Anatomy of a SQL Injection Incident, Part 2: Meat</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3017533</link><pubDate>Fri, 21 Mar 2008 18:52:58 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3017533</guid><dc:creator>neilcar</dc:creator><description>&lt;p&gt;It does sound correct although it looks like this is the third wave (Nov 07, Jan 08) of mass defacement via this or a similar attack.&lt;/p&gt;
&lt;p&gt;From the data I've looked at, all the affected pages were classic ASP and made SQL queries with data taken directly from query strings. &amp;nbsp;Other than that, the pages didn't appear to have any similarities. &amp;nbsp;I played around with building a SQL query that would generalize &amp;quot;any ASP page with a query string&amp;quot; but I didn't come up with one that worked. &amp;nbsp;Of course, it's likely that the attackers are smarter than me. &amp;nbsp;:)&lt;/p&gt;
</description></item><item><title>re: Anatomy of a SQL Injection Incident, Part 2: Meat</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3029631</link><pubDate>Sat, 05 Apr 2008 15:47:27 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3029631</guid><dc:creator>Kumar Atl</dc:creator><description>&lt;p&gt;Hello Sir,&lt;/p&gt;
&lt;p&gt;Could you spare 2 minutes for me also?&lt;/p&gt;
&lt;p&gt;I have a small website hosted on a shared plan. Hosting agency has provided me about 50 mb of sql server space.&lt;/p&gt;
&lt;p&gt;My site extensively uses asp and sql server. My site ranking is good with google for certain keywords searches.&lt;/p&gt;
&lt;p&gt;Friday morning I found that the bad people (nmidahena) had updated text fields in almost all of the tables with a &amp;lt;script&amp;gt; some thing.js &amp;lt;/script&amp;gt;. This has created a nightmare for me. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Fortunately, I had a backup that came to my rescue. I also downloaded all asp and html files to my local machines and searched for &amp;quot;nmidahena&amp;quot; - nothing came up.&lt;/p&gt;
&lt;p&gt;This is what I have done:&lt;/p&gt;
&lt;p&gt;a) Restore sql server tables from the backup.&lt;/p&gt;
&lt;p&gt;b) Rewrite my asp forms to not to accept any character or words that could be used for sql injection.&lt;/p&gt;
&lt;p&gt;Do you think this would be sufficient to prevent future attack?&lt;/p&gt;
&lt;p&gt; I dont know where to look for help. The hosting agency has no good answers. &lt;/p&gt;
&lt;p&gt;Sir, I will gladly pay your feel for your advise.&lt;/p&gt;
&lt;p&gt;with best regards&lt;/p&gt;</description></item><item><title>re: Anatomy of a SQL Injection Incident, Part 2: Meat</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3031748</link><pubDate>Mon, 07 Apr 2008 18:31:25 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3031748</guid><dc:creator>Tim Myers</dc:creator><description>&lt;p&gt;We were hit Friday night by nmidahena which is the newest edition of this virus. &amp;nbsp;Neil pegged it. &amp;nbsp;My quick fix was to create include code that parses the query string looking for DDL statements and flaging it with an error. &amp;nbsp;I get an email with each error so I can tweak the code if it is a false error. &amp;nbsp;I've already received one email showing sql injection. &amp;nbsp;My next step is to parameterize all queries. &amp;nbsp;&lt;/p&gt;</description></item><item><title>SQL Injection General Guidance</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3062050</link><pubDate>Wed, 28 May 2008 11:13:11 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3062050</guid><dc:creator>Microsoft Switzerland Security Blog</dc:creator><description>&lt;p&gt;There s a lot of noise arround currently ongoig SQL injection attacks and even if that is quite an &amp;quot;old&amp;quot;&lt;/p&gt;
</description></item><item><title>The latest SQL Injection Attacks</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3063326</link><pubDate>Fri, 30 May 2008 10:41:24 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3063326</guid><dc:creator>Roger's Security Blog</dc:creator><description>&lt;p&gt;Well, there was quite some chatter over the last few weeks with regards to the massive defacements we&lt;/p&gt;
</description></item><item><title>http://blogs.technet.com/swi/archive/2008/05/29/sql-injection-attack.aspx</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3063717</link><pubDate>Fri, 30 May 2008 21:12:34 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3063717</guid><dc:creator>TrackBack</dc:creator><description /></item><item><title>SQL注入攻击-来自微软安全博客的建议</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3066253</link><pubDate>Thu, 05 Jun 2008 06:01:08 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3066253</guid><dc:creator>Applelure</dc:creator><description>&lt;p&gt;本文翻译自微软博客上刊载的相关文章，英文原文版权归原作者所有，特此声明。（特别感谢NeilCarpenter对本文写作提供的帮助）&lt;/p&gt;
&lt;p&gt;近期趋势&lt;/p&gt;
&lt;p&gt;从去年下半年开始，很多网站被损害，他们在用于生成动...&lt;/p&gt;
</description></item><item><title>Inyección SQL... esta bajo ataque?</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3071787</link><pubDate>Mon, 16 Jun 2008 11:55:25 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3071787</guid><dc:creator>Todo es posible, nada es seguro</dc:creator><description>&lt;p&gt;Hay muchos sitios y blogs que hablan sobre el tema de inyecci&amp;#243;n SQL. Puede encontrar toda la informaci&amp;#243;n&lt;/p&gt;
</description></item><item><title>SQL Injection Tools</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3083183</link><pubDate>Thu, 03 Jul 2008 23:13:07 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3083183</guid><dc:creator>Theophilus</dc:creator><description>&lt;p&gt;Read a couple of blog posts about some fairly recent SQL Injection attacks (03 /08); &lt;a rel="nofollow" target="_new" href="http://blogs.technet"&gt;http://blogs.technet&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>SQL Injection Combat</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3083185</link><pubDate>Thu, 03 Jul 2008 23:15:56 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3083185</guid><dc:creator>Theophilus</dc:creator><description>&lt;p&gt;Read a couple of blog posts about some fairly recent SQL Injection attacks (03 /08); &lt;a rel="nofollow" target="_new" href="http://blogs.technet"&gt;http://blogs.technet&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Prevenindo SQL Injection - Ataques estranhos</title><link>http://blogs.technet.com/neilcar/archive/2008/03/15/anatomy-of-a-sql-injection-incident-part-2-meat.aspx#3243519</link><pubDate>Wed, 20 May 2009 05:37:15 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3243519</guid><dc:creator>Name of the blog</dc:creator><description>&lt;p&gt;Prevenindo SQL Injection - Ataques estranhos&lt;/p&gt;
</description></item></channel></rss>