<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Windows Zero-day &#8220;Animated Cursor&#8221; Vulnerability</title>
	<atom:link href="http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/</link>
	<description>tech, science, news and social issues for geeks</description>
	<pubDate>Mon, 13 Oct 2008 00:23:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: TheMatt</title>
		<link>http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/#comment-1814</link>
		<dc:creator>TheMatt</dc:creator>
		<pubDate>Sat, 07 Apr 2007 02:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/#comment-1814</guid>
		<description>As far as I know, the term "zero-day" applies the time between patch release and public knowledge.  If exploit code is publicly released before a patch for it is released.  This interpretation is backed up by an admittedly shaky &lt;a href="http://en.wikipedia.org/wiki/Zero-day_vulnerability" rel="nofollow"&gt;Wikipedia article&lt;/a&gt;.

I guess the point I got from this news is that it doesn't really matter when the vendor learns of a vulnerability...what's more important is the proximity of &lt;em&gt;public&lt;/em&gt; knowledge of the vulnerability, working exploit code, and the release of a patch to fix the vulnerability.  In this case, the advanced notice that Microsoft received from a responsible researcher was squandered when they failed to proactively release a patch before proof-of-concept code showed up in the wild and the vulnerability became public...and now it can be actively exploited until everyone's Windows Update will grab the patch.  And even then, autonomous worms will continue to propagate by this exploit when they can.

Also, it's important to note that "patch released" does not mean "vulnerability negated."  Any unpatched systems will still be vulnerable...and we all know that all manner of people don't know or care to update their systems.  That's why a clean, unpatched Windows install stays uninfected for mere minutes when connected to the public Internet.</description>
		<content:encoded><![CDATA[<p>As far as I know, the term &#8220;zero-day&#8221; applies the time between patch release and public knowledge.  If exploit code is publicly released before a patch for it is released.  This interpretation is backed up by an admittedly shaky <a href="http://en.wikipedia.org/wiki/Zero-day_vulnerability" rel="nofollow">Wikipedia article</a>.</p>
<p>I guess the point I got from this news is that it doesn&#8217;t really matter when the vendor learns of a vulnerability&#8230;what&#8217;s more important is the proximity of <em>public</em> knowledge of the vulnerability, working exploit code, and the release of a patch to fix the vulnerability.  In this case, the advanced notice that Microsoft received from a responsible researcher was squandered when they failed to proactively release a patch before proof-of-concept code showed up in the wild and the vulnerability became public&#8230;and now it can be actively exploited until everyone&#8217;s Windows Update will grab the patch.  And even then, autonomous worms will continue to propagate by this exploit when they can.</p>
<p>Also, it&#8217;s important to note that &#8220;patch released&#8221; does not mean &#8220;vulnerability negated.&#8221;  Any unpatched systems will still be vulnerable&#8230;and we all know that all manner of people don&#8217;t know or care to update their systems.  That&#8217;s why a clean, unpatched Windows install stays uninfected for mere minutes when connected to the public Internet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ursula</title>
		<link>http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/#comment-1791</link>
		<dc:creator>Ursula</dc:creator>
		<pubDate>Fri, 06 Apr 2007 23:27:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/#comment-1791</guid>
		<description>my laptop hasn't been the same since this FIX was forced on my system. What a joke. It moved system32 function of my AVG grisoft software so now my laptop is not protected with an antivirus. And the fix Microsoft suggests is another patch that has to do with some audio crap that has nothing to do with my machine. I am so mad I could scream.</description>
		<content:encoded><![CDATA[<p>my laptop hasn&#8217;t been the same since this FIX was forced on my system. What a joke. It moved system32 function of my AVG grisoft software so now my laptop is not protected with an antivirus. And the fix Microsoft suggests is another patch that has to do with some audio crap that has nothing to do with my machine. I am so mad I could scream.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2007-04-04 at Baron VC</title>
		<link>http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/#comment-1594</link>
		<dc:creator>links for 2007-04-04 at Baron VC</dc:creator>
		<pubDate>Wed, 04 Apr 2007 20:22:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/#comment-1594</guid>
		<description>[...] Windows Zero-day “Animated Cursor” Vulnerability Animated cursors? Hello? One of the reasons I love these guys (from afar). (tags: windows microsoft) [...]</description>
		<content:encoded><![CDATA[<p>[...] Windows Zero-day “Animated Cursor” Vulnerability Animated cursors? Hello? One of the reasons I love these guys (from afar). (tags: windows microsoft) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mackenzie</title>
		<link>http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/#comment-1462</link>
		<dc:creator>Mackenzie</dc:creator>
		<pubDate>Tue, 03 Apr 2007 01:46:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/#comment-1462</guid>
		<description>Doesn't zero-day mean the exploit is made public with "zero days of warning" to the company in charge (in this case, Microsoft)?  I'm pretty sure the day-count goes by when the company (or development team) is alerted to the issue, not when they get around to patching it.  It wouldn't exactly be a vulnerability if it's announced after the patches are already out.  Hey, Microsoft knew about the MS Word issues for months without patching them.</description>
		<content:encoded><![CDATA[<p>Doesn&#8217;t zero-day mean the exploit is made public with &#8220;zero days of warning&#8221; to the company in charge (in this case, Microsoft)?  I&#8217;m pretty sure the day-count goes by when the company (or development team) is alerted to the issue, not when they get around to patching it.  It wouldn&#8217;t exactly be a vulnerability if it&#8217;s announced after the patches are already out.  Hey, Microsoft knew about the MS Word issues for months without patching them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheMatt</title>
		<link>http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/#comment-1461</link>
		<dc:creator>TheMatt</dc:creator>
		<pubDate>Tue, 03 Apr 2007 01:35:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/#comment-1461</guid>
		<description>Even if it was announced by ZDNet last week, that's still significantly later than December 20th (which was when Microsoft was first made aware of this vulnerability by an independent researcher).  This puts it solidly in the realm of the "&lt;a href="http://en.wikipedia.org/wiki/Zero-day_vulnerability" rel="nofollow"&gt;zero-day&lt;/a&gt;" definition.  Proof-of-concept code is out in the wild well before Microsoft's patch is rolled out.</description>
		<content:encoded><![CDATA[<p>Even if it was announced by ZDNet last week, that&#8217;s still significantly later than December 20th (which was when Microsoft was first made aware of this vulnerability by an independent researcher).  This puts it solidly in the realm of the &#8220;<a href="http://en.wikipedia.org/wiki/Zero-day_vulnerability" rel="nofollow">zero-day</a>&#8221; definition.  Proof-of-concept code is out in the wild well before Microsoft&#8217;s patch is rolled out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mackenzie</title>
		<link>http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/#comment-1446</link>
		<dc:creator>Mackenzie</dc:creator>
		<pubDate>Mon, 02 Apr 2007 23:33:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.geeksaresexy.net/2007/04/02/windows-zero-day-animated-cursor-vulnerability/#comment-1446</guid>
		<description>If this was announced by ZDNet last week, I'm pretty sure it's disqualified from being called "zero-day."</description>
		<content:encoded><![CDATA[<p>If this was announced by ZDNet last week, I&#8217;m pretty sure it&#8217;s disqualified from being called &#8220;zero-day.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
