Vulnerabilities / Threats
7/11/2013
11:13 AM
50%
50%

Overcome The Microsoft Mindset: Patch Faster

Why can't vendors patch every critical bug like it was the Pwn2Own competition?

9 Android Apps To Improve Security, Privacy
9 Android Apps To Improve Security, Privacy
(click image for larger view)
Software vendors: Prepare to adjust your patching reality.

The long-running debate about how fast software vendors should be required to squash bugs in their products is heating up again, following Microsoft's release on July 9 of a fix for a critical bug that had been detailed publicly by Google security researcher Tavis Ormandy seven weeks prior. Microsoft said the bug had already been exploited in "targeted attacks."

Who's right and wrong in this scenario? Ormandy, for releasing full details of a bug and a working exploit, without giving Microsoft a courtesy call and time to code a fix? Or Microsoft, for dictating the terms of the game and generally giving itself lots of time to fix bugs that aren't being actively exploited?

[ How did a hacker hijack the Emergency Alert System? Read 'Zombie Apocalypse' Broadcast Hoax Explained. ]

Regardless of your take, Google seems set to rewrite the rules of the bug-patching game, after two of its security researchers, Chris Evans and Drew Hintz, issued a warning to vendors in a May blog post: In cases of "critical vulnerabilities under active exploitation," Google will now give vendors only seven days to release a patch. After that time, Google will issue full details of the vulnerability. For anything that's not critical, Google is sticking with its recommendation to fix bugs within 60 days or else issue workarounds and mitigation techniques to affected users.

While acknowledging that the seven-day timeline is "aggressive," Evans and Hintz said everyone stands to benefit. "By holding ourselves to the same standard, we hope to improve both the state of Web security and the coordination of vulnerability management," they said in their post.

Google's revised bug-disclosure timeline is good news for all software users. "It shows that the long timeframes that the industry has been operating under -- find a vulnerability, ensure it's fixed within six months or a year -- isn't adequate," SANS Institute fellow Ed Skoudis told me in a phone interview. "So Google is trying to juice the whole thing to make it happen faster."

Skoudis added: "Microsoft got us into this mindset: You find a flaw, responsibly tell a vendor, and darn it, there will be a fix out within a year."

The annual Pwn2Own competition, hosted by Hewlett-Packard's DVLabs Zero Day Initiative (ZDI), has also been reshaping our collective patching mindset. "Google and Mozilla were able to patch the issues that were being exploited in the competition in less than two days," said ZDI manager Brian Gorenc, speaking by phone. Of course, it was in both companies' best interests to patch their browsers quickly, thus making Chrome and Firefox look better than Internet Explorer. "For actively exploited bugs, they pose an immediate problem for vendors, and they need to be pressured to act quickly," Gorenc said.

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
MartinRH
50%
50%
MartinRH,
User Rank: Apprentice
7/14/2013 | 5:25:54 AM
re: Overcome The Microsoft Mindset: Patch Faster
Great piece Mathew. It will be interesting and useful to see if and/or how this pans out. "go git 'em Google!" ;-)
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-2015-0192
Published: 2015-07-02
Unspecified vulnerability in IBM Java 8 before SR1, 7 R1 before SR2 FP11, 7 before SR9, 6 R1 before SR8 FP4, 6 before SR16 FP4, and 5.0 before SR16 FP10 allows remote attackers to gain privileges via unknown vectors related to the Java Virtual Machine.

CVE-2015-1914
Published: 2015-07-02
IBM Java 7 R1 before SR3, 7 before SR9, 6 R1 before SR8 FP4, 6 before SR16 FP4, and 5.0 before SR16 FP10 allows remote attackers to bypass "permission checks" and obtain sensitive information via vectors related to the Java Virtual Machine.

CVE-2015-1916
Published: 2015-07-02
Unspecified vulnerability in IBM Java 8 before SR1 allows remote attackers to cause a denial of service via unknown vectors related to SSL/TLS and the Secure Socket Extension provider.

CVE-2015-3157
Published: 2015-07-02
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.

CVE-2015-3202
Published: 2015-07-02
fusermount in FUSE before 2.9.3-15 does not properly clear the environment before invoking (1) mount or (2) umount as root, which allows local users to write to arbitrary files via a crafted LIBMOUNT_MTAB environment variable that is used by mount's debugging feature.

Dark Reading Radio
Archived Dark Reading Radio
Marc Spitler, co-author of the Verizon DBIR will share some of the lesser-known but most intriguing tidbits from the massive report