Google relaxes disclosure policy following criticism

Posted by   Virus Bulletin on   Feb 16, 2015

Grace period added for vulnerabilities that are about to be patched.

Last year, Google announced a new disclosure policy, where details of a vulnerability discovered by the company's researchers would be published within 90 days of the affected vendor being notified, regardless of whether or not a patch had been released. If the vulnerability were to be actively exploited in the wild, details would even be disclosed within seven days.

This policy has been controversial to say the least, with many arguing that patching can be complicated, especially when a vulnerability is buried deep inside the code. When, last month, Google published details of a privilege escalation vulnerability in Windows 8.1 just days before Microsoft issued a patch, many saw it as irresponsible on Google's part.

I have mixed feelings about this issue. On the one hand, Google's policy adds clarity to the disclosure debate. Even when vulnerabilities are disclosed responsibly, it can take vendors a very long time to patch, leaving customers at risk and making researchers feel that they might as well sell their discoveries on underground markets.

On the other hand, I feel a bit uncomfortable about Google unilaterally deciding what's best for the Internet. And some recent cases do make one wonder whether it's really in everyone's interest that details of a vulnerability are disclosed a matter of days before a patch is released.

Thankfully, Google is not immune to criticism and has responded by relaxing its policy in two ways.

Firstly, disclosure will never take place during weekends or public holidays; in such cases the deadline will be moved to the next working day.

Secondly, a 14-day 'grace period' has been added for vulnerabilities that will be fixed within two weeks of the 90-day deadline. This should prevent cases like the one affecting Microsoft where the vendor has a patch ready, yet is running some QA-tests, or is waiting for its own patch cycle.

I think Google has made some very reasonable concessions here, without significantly compromising on the essential message of its program: patch quickly, or someone will exploit the vulnerability.

Posted on 16 February 2015 by Martijn Grooten

twitter.png
fb.png
linkedin.png
hackernews.png
reddit.png

 

Latest posts:

New paper: LokiBot: dissecting the C&C panel deployments

First advertised as an information stealer and keylogger when it appeared in underground forums in 2015, LokiBot has added various capabilities over the years and has affected many users worldwide. In a new paper researcher Aditya Sood analyses the…

VB2019 presentation: Building secure sharing systems that treat humans as features not bugs

In a presentation at VB2019 in London, Virtru's Andrea Limbago described how, by exploring data sharing challenges through a socio-technical lens, it is possible to make significant gains toward the secure sharing systems and processes that are vital…

VB2019 presentation: Attor: spy platform with curious GSM fingerprinting

Attor is a newly discovered cyber-espionage platform, use of which dates back to at least 2014 and which focuses on diplomatic missions and governmental institutions. Details of Attor were presented at VB2019 in London by ESET researcher Zuzana…

Why we encourage newcomers and seasoned presenters alike to submit a paper for VB2020

With the call for papers for VB2020 currently open, we explain why, whether you've never presented before or you're a conference circuit veteran, if you have some interesting research to share with the community we want to hear from you!

VB2019 paper: The cake is a lie! Uncovering the secret world of malware-like cheats in video games

At VB2019 in London, Kaspersky researcher Santiago Pontiroli presented a paper on the growing illegal economy around video game cheats and its parallels with the malware industry. Today we publish both Santiago's paper and the recording of his…

We have placed cookies on your device in order to improve the functionality of this site, as outlined in our cookies policy. However, you may delete and block all cookies from this site and your use of the site will be unaffected. By continuing to browse this site, you are agreeing to Virus Bulletin's use of data as outlined in our privacy policy.