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
googleplus.png
reddit.png

 

Latest posts:

Throwback Thursday: Giving the EICAR test file some teeth

The 68-byte EICAR test file plays as important a role today as it did 19 years ago. In this week's Throwback Thursday we look back at a VB99 conference paper in which Randy Abrams described how this 'miracle tool' worked and how it could be used.

XMRig used in new macOS cryptominer

A new piece of cryptocurrency-mining malware on macOS has been found to use the popular XMRig miner.

Tendency for DDoS attacks to become less volumetric fits in a wider trend

CDN provider Cloudflare reports an increase in DDoS attacks targeting layer 7 and focusing on exhausting server resources rather than sending large volumes of data. This fits in a wider trend.

Turkish Twitter users targeted with mobile FinFisher spyware

Through fake social media accounts, users were tricked into installing an Android application that was actually a mobile version of the FinFisher spyware.

Hide'n'Seek IoT botnet adds persistence

The Hide'n'Seek IoT botnet has received an update to make its infection persist on infected devices beyond a restart.