Commentary

Dave Methvin
 

Google-Disclosed Hole Being Exploited

Less than a week after Google security researcher Tavis Ormandy disclosed a security problem with the Windows Help application, attackers are exploiting the hole on Windows XP. Their work was simple since he provided proof-of-concept code.

Less than a week after Google security researcher Tavis Ormandy disclosed a security problem with the Windows Help application, attackers are exploiting the hole on Windows XP. Their work was simple since he provided proof-of-concept code.This is exactly the situation I feared would happen a few days ago, and it didn't take long for the bad guys to deliver. Sophos has seen an exploit in the wild. Microsoft has a emergency fix that disables the feature being exploited, and you may want to use it in your company.

This harsh publicity has put Ormandy on the defensive; he recently tweeted, "I'm getting pretty tired of all the '5 days' hate mail. Those five days were spent trying to negotiate a fix within 60 days." That's in reference to earlier concerns Ormandy expressed about how slowly Microsoft was fixing bugs. If that's the case, why not just tell them they had 60 days before the exploit would be revealed, rather than five?


More Windows Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Some of the commenters on my previous post seemed to blame Microsoft for this situation. I completely disagree. There is no way that Microsoft could reasonably respond to something like this in only five days. The "Windows is full of bugs" argument doesn't wash, either; every OS has its bugs. No responsible security researcher should be making a decision to release an exploit for an operating system without giving the OS maker a reasonable chance to respond. That's doubly true for a researcher employed by Google, a competitor to Microsoft.


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