<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.iis.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/" xmlns:cs="http://blogs.iis.net/"><channel><title>Dave&amp;#39;s Blog : ASP</title><link>http://blogs.iis.net/davcox/archive/tags/ASP/default.aspx</link><description>Tags: ASP</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>3 Years and 3 months</title><link>http://blogs.iis.net/davcox/archive/2006/07/21/3-years-and-3-months.aspx</link><pubDate>Fri, 21 Jul 2006 18:44:00 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:1348277</guid><dc:creator>davcox</dc:creator><slash:comments>1</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.iis.net/davcox/rsscomments.aspx?PostID=1348277</wfw:commentRss><wfw:comment xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://blogs.iis.net/davcox/commentapi.aspx?PostID=1348277</wfw:comment><comments>http://blogs.iis.net/davcox/archive/2006/07/21/3-years-and-3-months.aspx#comments</comments><description>&lt;P&gt;&lt;FONT face=Arial color=#000000 size=2&gt;Windows Server&amp;nbsp;2003 and IIS6 released in March of 2003.&amp;nbsp; Last week, we released a patch for asp.dll to fix our first vulnerability in over 3 years!&amp;nbsp; &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face=Arial color=#000000 size=2&gt;It was kind of a sad day for the team (but one that we knew would come), because after IIS5, we&amp;nbsp;committed as a team&amp;nbsp;to never let IIS be an primary attack vector for the Windows platform.&amp;nbsp; And so far we've been able to keep that commitment.&amp;nbsp; Hopefully it'll be another 3 years before we release another one!&amp;nbsp; :)&amp;nbsp; So it was also a happy day in that 3 years is a really long time (these days) for your product to be really&amp;nbsp;"unbreakable".&amp;nbsp; :)&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face=Arial color=#000000 size=2&gt;I had the duty of testing the patch before it was released to make sure the vulnerability was indeed fixed.&amp;nbsp; Ulad did a great job of doing a very thorough analysis of the code and a thorough fix to the issue.&amp;nbsp; Given that we hadn't shipped a release like this in 3 years we did have a couple hicups, you might have seen or experienced this issue:&amp;nbsp; &lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"&gt;&lt;A title=http://news.com.com/Microsoft+irons+out+security+patch/2100-1002_3-6096179.html?tag=newsmap href="http://news.com.com/Microsoft+irons+out+security+patch/2100-1002_3-6096179.html?tag=newsmap" mce_href="http://news.com.com/Microsoft+irons+out+security+patch/2100-1002_3-6096179.html?tag=newsmap"&gt;&lt;FONT color=#0000ff&gt;http://news.com.com/Microsoft+irons+out+security+patch/2100-1002_3-6096179.html?tag=newsmap&lt;/FONT&gt;&lt;/A&gt;&lt;FONT color=#000000&gt;&amp;nbsp;&amp;nbsp;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"&gt;&lt;FONT color=#000000&gt;That issue was mostly due to the "detectoid" logic that WU uses to say if the patch is needed or not; the patch itself was fine (so no work was required on the IIS side) although I spent a long night here last week to help them pinpoint the issue.&amp;nbsp; &lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"&gt;&lt;FONT color=#000000&gt;Also, we were unable to get the right logic to restart w3svc prior to updating the asp.dll binary, but there is an easy workaround for that.&amp;nbsp; Next time, (if there is a next time) we'll be sure to get that logic correct.&amp;nbsp; &lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;FONT face=Arial color=#000000 size=2&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"&gt;&lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/FONT&gt;
&lt;P&gt;&lt;FONT face=Arial color=#000000 size=2&gt;As the MSRC bulletin says, this vulnerability requires the attacker to place asp content on the machine (so for example hosting scenarios).&amp;nbsp; Once the maliciously formed page is requested, the attacker would be able to run arbitrary code.&amp;nbsp; So it's certainly an important patch to install.&amp;nbsp; There is extremely little risk in installling this patch given the nature of the code change and the testing that we did on this patch.&amp;nbsp; &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face=Arial color=#000000 size=2&gt;Anyway, I'm glad to be back blogging, I had some permissions and user account problems blocking me.&amp;nbsp; &lt;/FONT&gt;&lt;/P&gt;&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=1348277" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/davcox/archive/tags/IIS6/default.aspx">IIS6</category><category domain="http://blogs.iis.net/davcox/archive/tags/Security/default.aspx">Security</category><category domain="http://blogs.iis.net/davcox/archive/tags/ASP/default.aspx">ASP</category></item></channel></rss>