Google Security Pushes for 7-Day Vulnerability Publishing
May 30, 2013 2:29 PM
comment(s) - last by
This could encourage companies to issue security patches more quickly
is backing a new seven-day deadline that would allow researchers to make serious vulnerabilities public a week after notifying a company.
Google security engineers Chris Evans and Drew Hintz said they want critical vulnerabilities under active exploitation to be published seven days after researchers have informed the company about them. They said this will lead to quicker patches and cut the risk of further problems in the future.
“Our standing recommendation is that companies should fix critical vulnerabilities within 60 days — or, if a fix is not possible, they should notify the public about the risk and offer workarounds,” said Evans and Hintz. “We encourage researchers to publish their findings if reported issues will take longer to patch. Based on our experience, however, we believe that more urgent action — within seven days — is appropriate for critical vulnerabilities under active exploitation. The reason for this special designation is that each day an actively exploited vulnerability remains undisclosed to the public and unpatched, more computers will be compromised.”
Right now, companies use either responsible disclosure or full disclosure when dealing with vulnerabilities. Responsible disclosure allows a company as much time as they want to patch an exploit, and the details surrounding the bug aren't revealed to the public until a patch is issued. Full disclosure, on the other hand, means the company and the public are given information about the flaw at the same time.
Three years ago, Google's security team introduced a 60-day notice in order to find a happy medium between the two disclosures. This meant that researchers could publish details about a flaw for the public to see after 60 days whether a patch was issued or not.
But it looks like Google is taking this a giant step further by advocating a new seven-day deadline, where researchers can make details about a flaw public only a week after telling the company about it.
However, Google realizes that seven days is not enough time to patch all vulnerabilities. Even if a company can't address the bug in seven days, the researchers could still publish the details of the software flaw after a week so that the public can protect itself.
Earlier this month, Google security engineer Tavis Ormandy
exposed a Microsoft flaw
on Full Disclosure. The Microsoft vulnerability, which was in the Windows kernel driver "Win32k.sys," was featured in a Full Disclosure mailing list on May 17.
Ormandy also insulted Microsoft on Full Disclosure, saying "As far as I can tell, this code is pre-NT (20+ years) old, so remember to thank the SDL for solving security and reminding us that old code doesn't need to be reviewed ;-)."
Microsoft has been annoyed with Ormandy for publicly discussing vulnerabilities before they could be patched. Microsoft prefers "responsible disclosure," where security experts are asked to report flaws privately to the company.
Google Online Security Blog
This article is over a month old, voting and posting comments is disabled
RE: Patch tuesday
5/30/2013 2:55:15 PM
Yea you know where this is coming from.
Does everyone trust 7 day test periods? I dont.
RE: Patch tuesday
5/30/2013 3:17:06 PM
I do. Why would you need longer? If the patch doesn't impact services for 7 days throughout multiple scheduled tasks and procedures, why waste time and ask for longer test periods?
RE: Patch tuesday
5/30/2013 3:41:53 PM
Originally MS released patches as they were completed which resulted new patches coming out every few days. The monthly cycle (for bugs not being actively exploited) was due to pushback from corporate IT. They objected for cost reasons to having to run regression testing for their applications/systems multiple times per week and to the downtime that resulted from having to restart servers to patch them that frequently as well.
"It's okay. The scenarios aren't that clear. But it's good looking. [Steve Jobs] does good design, and [the iPad] is absolutely a good example of that." -- Bill Gates on the Apple iPad
Google Engineer Finds Microsoft Security Flaw, Says Company is Hostile About It
May 23, 2013, 10:51 AM
Netflix Announces 7-to-1 Stock Split, Eyes Explosive Overseas Growth
June 23, 2015, 8:18 PM
Sources: Hack on Fed. Database Lost 4.1M Social Security Numbers, Personal Info
June 11, 2015, 9:11 PM
The Big One: Chinese Hackers Steal Records of 4 Million U.S. Gov. Employees
June 4, 2015, 8:13 PM
Tutorial: Here's How to Force YouTube or Vimeo VIdeos to Embed as HTML5
June 3, 2015, 10:14 PM
Google Finally Fixes Maps Bug That Was Giving Racist, Profane Results
May 21, 2015, 1:43 PM
The Pirate Bay Loses Its Iconic Swedish Dot SE Domains
May 20, 2015, 6:31 PM
Most Popular Articles
F-16 Schools Trillion-Dollar F-35 in Mock Combat, Fleeing is Best Option Pilot Admits
July 1, 2015, 5:53 PM
Apple Music: The Money, The Launch Hiccups, and the Nitty Gritty Details
June 30, 2015, 5:09 PM
Quick Note: Lumia 940 XL "Cityman" Phablet Gets Teased Via Tests
June 29, 2015, 5:51 PM
SpaceX Falcon 9's Seventh Supply Mission to ISS Ends w/ Fiery Stage 1 Explosion
June 28, 2015, 1:10 PM
Windows XP, Vista Users Can Get Free Windows 10 Upgrade Thanks to Loophole
June 23, 2015, 2:23 PM
Latest Blog Posts
Sceptre Airs 27", 120 Hz. 1080p Monitor/HDTV w/ 5 ms Response Time for $220
Dec 3, 2014, 10:32 PM
Costco Gives Employees Thanksgiving Off; Wal-Mart Leads "Black Thursday" Charge
Oct 29, 2014, 9:57 PM
"Bear Selfies" Fad Could Turn Deadly, Warn Nevada Wildlife Officials
Oct 28, 2014, 12:00 PM
The Surface Mini That Was Never Released Gets "Hands On" Treatment
Sep 26, 2014, 8:22 AM
ISIS Imposes Ban on Teaching Evolution in Iraq
Sep 17, 2014, 5:22 PM
More Blog Posts
Copyright 2015 DailyTech LLC. -
Terms, Conditions & Privacy Information