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:

VB2018 paper: The modality of mortality in domain names

Domains play a crucial role in most cyber attacks, from the very advanced to the very mundane. Today, we publish a VB2018 paper by Paul Vixie (Farsight Security) who undertook the first systematic study into the lifetimes of newly registered domains.…

VB2018 paper: Analysing compiled binaries using logic

Constraint programming is a lesser-known technique that is becoming increasingly popular among malware analysts. In a paper presented at VB2018 Thaís Moreira Hamasaki presented an overview of the technique and explained how it can be applied to the…

Virus Bulletin encourages experienced speakers and newcomers alike to submit proposals for VB2019

With a little less than a month before the deadline of the call for papers for VB2019, Virus Bulletin encourages submissions from experienced speakers and newcomers alike.

VB2018 paper: Internet balkanization: why are we raising borders online?

At VB2018 in Montreal, Ixia researcher Stefan Tanase presented a thought-provoking paper on the current state of the Internet and the worrying tendency towards raising borders and restricting the flow of information. Today we publish both his paper…

The malspam security products miss: banking and email phishing, Emotet and Bushaloader

The set-up of the VBSpam test lab gives us a unique insight into the kinds of emails that are more likely to bypass email filters. This week we look at the malspam that was missed: banking and email phishing, Emotet and Bushaloader.

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.