Vulnerabilities / Threats
8/4/2010
07:55 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Researchers Throw Down Vulnerability-Disclosure Gauntlet

TippingPoint's Zero Day Initiative (ZDI) program institutes deadline of six months for vendors to fix bugs -- or else the bugs get published

First it was Google drawing a line in the sand with a 60-day deadline for vendors to fix vulnerabilities it finds in their products before going public. Now it's TippingPoint's Zero Day Initiative (ZDI), which officially announced today it has set a six-month time frame from when it reports a bug to a vendor until it goes public with it.

ZDI, which historically has worked with vendors in not disclosing any bugs it finds until they patch them, says some vendors are getting a little too comfortable with that open-ended agreement. ZDI has 31 high-risk vulnerabilities on its docket that have been awaiting patches for more than a year: "We have some bulletins that are 3 years old," says Aaron Portnoy, manager of security researcher for ZDI. "The longer we sit on these, the longer people are exposed to [the threats]. Letting vendors take as much time as they needed, they took more time than they needed ... and there were no repercussions for them, but more work for us."

Aside from Google and now ZDI, Rapid7 also recently set a deadline for bug disclosures of 15 days: If a vendor hasn't patched it by then, Rapid7 reports the bug to CERT, which gives vendors 45 days to patch from the initial report date before it goes public.

But Microsoft has stood firm in its refusal to place a timetable on when it issues patches for reported bugs. Mike Reavey, director of Microsoft Security Response Center, contends that patch deadlines aren't the answer because it's not a "one-size-fits-all" time frame for fixing vulnerabilities -- some just take longer to fix than others. It's a delicate balance between quality and timeliness given that Microsoft puts the patches through a hefty testing process before issuing them, he says.

ZDI's new policy applies to currently outstanding vulnerabilities it has reported to vendors, as well as any it finds from now on. If the vendor doesn't patch by the six-month mark, then ZDI will publish a "limited" advisory that includes mitigation options for users. But ZDI says it will allow vendors to ask for extensions for difficult patches. "If any vulnerability is given an extension we plan on publishing the communication we've had with the vendor regarding the issue once it is patched," Portnoy blogged today.

Google called it irresponsible for vendors to leave a flaw unfixed for a long period of time -- this can drag on for years sometimes, Google researchers say. So from now on, any serious bug they report must be fixed within the 60-day deadline; if the vendor doesn't fix it within that time frame, Google will publish an analysis of the bug as well as any workarounds.

HD Moore, chief security officer at Rapid7 and chief architect of Metasploit, says you can tell within 60 days whether a vendor is going to prioritize a fix, anyway. "ZDI got fed up ... For them, it was a big drain to manage and keep track of them all," Moore says.

A big trend in vulnerability discovery of late is that, increasingly, different researchers are coincidentally finding the same bugs, some within weeks of one another, so the lines are blurring, researchers say.

What about the risk of bad guys getting hold of the unpatched bug once it's published? ZDI, Google, and Rapid7 researchers contend that holding off on fixing a bug is riskier, especially since many newly discovered bugs have already been found by other researchers. A deadline for vendors is an attempt to close the gap between discovery and patching, they say.

"I hope more companies will do this ... with a fixed disclosure schedule," Moore says. "Then vendors have to take it seriously to go out and fix it."

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3352
Published: 2014-08-30
Cisco Intelligent Automation for Cloud (aka Cisco Cloud Portal) 2008.3_SP9 and earlier does not properly consider whether a session is a problematic NULL session, which allows remote attackers to obtain sensitive information via crafted packets, related to an "iFrame vulnerability," aka Bug ID CSCuh...

CVE-2014-3908
Published: 2014-08-30
The Amazon.com Kindle application before 4.5.0 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.

CVE-2010-5110
Published: 2014-08-29
DCTStream.cc in Poppler before 0.13.3 allows remote attackers to cause a denial of service (crash) via a crafted PDF file.

CVE-2012-1503
Published: 2014-08-29
Cross-site scripting (XSS) vulnerability in Six Apart (formerly Six Apart KK) Movable Type (MT) Pro 5.13 allows remote attackers to inject arbitrary web script or HTML via the comment section.

CVE-2013-5467
Published: 2014-08-29
Monitoring Agent for UNIX Logs 6.2.0 through FP03, 6.2.1 through FP04, 6.2.2 through FP09, and 6.2.3 through FP04 and Monitoring Server (ms) and Shared Libraries (ax) 6.2.0 through FP03, 6.2.1 through FP04, 6.2.2 through FP08, 6.2.3 through FP01, and 6.3.0 through FP01 in IBM Tivoli Monitoring (ITM)...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.