Bugs to be reported to the vendor only, and to become public once patched.
Google
has
created
a new team, called Project Zero, whose task is to find vulnerabilities in any kind of widely used software and to report them to the respective vendor.
Few subjects in security are as controversial as the disclosure of zero-day vulnerabilities. Some argue that vulnerabilities should always be reported to the affected vendor, and that a ‘bug bounty’ is a nice, but not mandatory extra. Others say that without a bug bounty rewarding the researchers for their work, they shouldn’t report it – and even if there is a reward, the bug should only be reported if the bounty is deemed reasonable.
Indeed, bug bounties aren’t the only way researchers can monetize the vulnerabilities they find: there are various entities that will gladly pay for such vulnerabilities, some of which aren’t always seen to have the best interests of the average Internet user at heart. This has led to calls to regulate the sale of zero-days, and in response, strongly voiced opinions that such regulation would be a bad idea, and would violate the researchers’ right to free speech.
None of the vulnerabilities found by
Google
will be reported to third-parties, though: only the affected vendor will be notified, and will be given time to patch. Once the bug has been made public (which,
Google
says, will typically happen “once a patch is available”), it will be added to a public database. This allows anyone to monitor the time it takes vendors to fix vulnerabilities.
Unless you have an interest in the use or sale of vulnerabilities, it is hard not to see this as a good development.
Google
researchers have already discovered a number of high-profile vulnerabilities, with
Heartbleed
being the most prominent among them. The fact that they have now set up a team dedicated to finding vulnerabilities is in the interest of Internet users in general, and likely potential victims of targeted attacks in particular.
Posted on 16 July 2014 by
Martijn Grooten
Leave a Reply