Linked by Thom Holwerda on Wed 15th Apr 2009 09:54 UTC
Permalink for comment 358699
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2006-01-02
MS has a bit more involved system for a few reasons. First, there's a functional test pass of the component and all downstream items to ensure nothing is broken.
At the same time, the security response team reviews the code in the area or any similar code for the same bug.
Then there's the creation of appropriate bulletins translated into a number of languages for worldwide distribution.
Lastly, the patch is distributed during the normal patching cycle unless it is being actively exploited. This is done to make the testing job easier for IT admins. Of course this rule is broken if there are active exploits in the wild.
Usually the time to patch is not the most important factor since most of the famous attacks (Nimda, Code Red, Slammer, and now Conficker) were not exploited by the original discoverers. They were instead exploited by people reverse-engineering a long-released patch (9-12 months in the case of Slammer).
Vulnerabilities will always slip through the cracks, though we try to catch most of them during development by fuzzing and review (I've personally prevented a couple of little NT kernel EoPs). In Vista and later OS releases, this particular exploit is less effective due to better containment of the vulnerable code.