Commentary

George Hulme
 

Much Ado Over Microsoft's (Somewhat) Rare Out-Of-Band Patch

My advice: Patch this puppy, and don't worry about whether or not Microsoft should have published this update out of its normal monthly update cycle.

My advice: Patch this puppy, and don't worry about whether or not Microsoft should have published this update out of its normal monthly update cycle.Last week, right on Patch Tuesday, in fact, Microsoft learned of a zero-day vulnerability, and toward the end of the week, it was being widely exploited.

The first point is that more zero-days are being released on, or right after, Patch Tuesday. This is no doubt a tactic designed to maximize the shelf life of the exploit. I fully expect this trend to increase, especially as more software vendors publish software security updates on a standard schedule. I still think this practice reaps more benefit than harm: without it, there would be more zero-day attacks and we'd be patching our systems every week. That drains enterprise resources.


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Second: Microsoft had to release this patch because the vulnerability was being exploited, and users could get attacked just by visiting a Web site -- even so-called trusted Web sites. It was getting nasty.

As was explained to Thomas Claburn in this story:

"The browser flaw had been disclosed roughly one week ago as a zero-day vulnerability, and active exploits have been around the Internet for that time frame as well," Qualys CTO Wolfgang Kandek said in an e-mailed statement. "The workarounds provided by Microsoft were very technical and quite cumbersome to implement, making it imperative for Microsoft to release a fix as quickly as possible."

That sums it up well. The workarounds were quite kludgey.

However, I have to take partial issue with this take from Roel Schouwenberg, senior antivirus researcher with Kaspersky Lab, Americas, on what this flaw's lack of wormability, and subsequent out-of-band patch, means:

"[That] shows that the wormability of a vulnerability is no longer a good indicator of the seriousness of a threat and that these Web-based threats are now much more dangerous than network worms," said Roel Schouwenberg, senior antivirus researcher for Kaspersky Lab, Americas, in an e-mailed statement.

I see his point, and actually agree that Web-based threats are both more prevalent and more dangerous (in many scenarios I can think of) than network worms. However, "worm ability" is still a strong indicator of the seriousness of a threat.

And we will see more Web-based worms in the future. Why? Because they're more profitable than network worms. The age of network worms died largely because there's more profit to develop exploits that can make a buck: not worms that essentially cause widespread denial-of-service situations.

Wormable or not. Whether Microsoft should have gone out-of-band with this one, or not. You need to patch MS08-078.

Eric Schultze, CTO at Shavlik Technologies, e-mailed me an interesting wager: "I'd bet you a cookie that many companies can't get it rolled out as quickly as Microsoft got it built."

I'll bet he's right.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links