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
Video
Cartoon
Current Issue
Flash Poll
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-3308
Published: 2015-09-02
Double free vulnerability in lib/x509/x509_ext.c in GnuTLS before 3.3.14 allows remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted CRL distribution point.

CVE-2015-4330
Published: 2015-09-02
A local file script in Cisco TelePresence Video Communication Server (VCS) Expressway X8.5.2 allows local users to gain privileges for OS command execution via invalid parameters, aka Bug ID CSCuv10556.

CVE-2015-6274
Published: 2015-09-02
The IPv4 implementation on Cisco ASR 1000 devices with software 15.5(3)S allows remote attackers to cause a denial of service (ESP QFP CPU consumption) by triggering packet fragmentation and reassembly, aka Bug ID CSCuv71273.

CVE-2015-6277
Published: 2015-09-02
The ARP implementation in Cisco NX-OS on Nexus 1000V devices for VMware vSphere 5.2(1)SV3(1.4), Nexus 3000 devices 7.3(0)ZD(0.47), Nexus 4000 devices 4.1(2)E1, Nexus 9000 devices 7.3(0)ZD(0.61), and MDS 9000 devices 7.0(0)HSK(0.353) and SAN-OS NX-OS on MDS 9000 devices 7.0(0)HSK(0.353) allows remote...

CVE-2015-6587
Published: 2015-09-02
The vlserver in OpenAFS before 1.6.13 allows remote authenticated users to cause a denial of service (out-of-bounds read and crash) via a crafted regular expression in a VL_ListAttributesN2 RPC.

Dark Reading Radio
Archived Dark Reading Radio
Another Black Hat is in the books and Dark Reading was there. Join the editors as they share their top stories, biggest lessons, and best conversations from the premier security conference.