Feeds

Spurned security researchers form anti-MS collective

There's power in a union

High performance access to file storage

Updated Security researchers irked by how Microsoft responded to Google engineer Tavis Ormany's public disclosure of a zero-day Windows XP Help Center security bug have banded together to form a group called the Microsoft Spurned Researcher Collective*.

The group is forming a "union" in the belief that together they will be better placed to handle flak from Redmond and elsewhere following the publication of security flaws. A statement, published by The Windows Club blog, explains the Collective's stance.

“Due to hostility toward security researchers, the most recent example being of Tavis Ormandy, a number of us from the industry (and some not from the industry) have come together to form MSRC: the Microsoft-Spurned Researcher Collective," it said. "MSRC will fully disclose vulnerability information discovered in our free time, free from retaliation against us or any inferred employer.”

Last week the researcher published a zero day flaw affecting Windows Vista and Windows Server 2008. The unpatched security bug creates a means for hackers to crash affected systems and stems from a security bug in the Windows kernel. Vupen Security, which published an advisory on the flaw but is not part of the collective (Contrary to early versions of this story, Vupen rates the vulnerability only as a moderate risk bug because it doesn't lend itself to remote execution.)

The debate about responsible disclosure of security vulnerabilities is as old as software development. Security researchers argue that by disclosing problems they give end-users a chance to act and put pressure to act on software developers, who might otherwise be tempted to ignore the problem. Software developers (including Oracle, Adobe and many others as well as MS) argue that disclosing vulnerabilities in the absence of a fix imperils users.

To some outside either camp the argument hinges on whether a vulnerability is been actively exploited. The length of time a vendor has had to fix a bug - a period that can sometimes run into months - is also an important factor. ®

* The name of the group is an obvious send-up of Redmond's own Microsoft Security Response Centre.

High performance access to file storage

More from The Register

next story
Obama allows NSA to exploit 0-days: report
If the spooks say they need it, they get it
Parent gabfest Mumsnet hit by SSL bug: My heart bleeds, grins hacker
Natter-board tells middle-class Britain to purée its passwords
Web data BLEEDOUT: Users to feel the pain as Heartbleed bug revealed
Vendors and ISPs have work to do updating firmware - if it's possible to fix this
OpenSSL Heartbleed: Bloody nose for open-source bleeding hearts
Bloke behind the cockup says not enough people are helping crucial crypto project
One year on: diplomatic fail as Chinese APT gangs get back to work
Mandiant says past 12 months shows Beijing won't call off its hackers
Call of Duty 'fragged using OpenSSL's Heartbleed exploit'
So it begins ... or maybe not, says one analyst
Experian subsidiary faces MEGA-PROBE for 'selling consumer data to fraudster'
US attorneys general roll up sleeves, snap on gloves
Oz bank in comedy Heartbleed blog FAIL
Bank: 'We are now safely patched.' Customers: 'You were using OpenSSL?'
prev story

Whitepapers

Mainstay ROI - Does application security pay?
In this whitepaper learn how you and your enterprise might benefit from better software security.
Five 3D headsets to be won!
We were so impressed by the Durovis Dive headset we’ve asked the company to give some away to Reg readers.
3 Big data security analytics techniques
Applying these Big Data security analytics techniques can help you make your business safer by detecting attacks early, before significant damage is done.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Mobile application security study
Download this report to see the alarming realities regarding the sheer number of applications vulnerable to attack, as well as the most common and easily addressable vulnerability errors.