Vulnerabilities / Threats
11:25 AM

Google Patches Critical Chrome Bug

Chrome browser update includes patches for 11 vulnerabilities, including several discovered by Google bug bounty winners.

10 Essential Google+ Tips
Slideshow: 10 Essential Google+ Tips
(click image for larger view and for slideshow)
Google released a new version (13.0.782.215) of its Chrome browser Monday that includes patches for 11 vulnerabilities. Nine of the vulnerabilities are rated as being of "high" severity, while one is "medium." The other, meanwhile, is "critical," which is Google's ranking for the most severe vulnerabilities found.

That bug is the sixth critical vulnerability in Chrome discovered in 2011 and relates to "memory corruption in vertex handing"--code that handles three-dimensional rendering--in the Windows version of Chrome. Credit for discovering the bug was given to Michael Braithwaite, a senior engineer at Turbulenz, and it earned him $1,337 from Google.

According to the Google Chromium blog, Michel Aubizziere (aka "miaubiz"), a regular Google bug bounty winner, found two new bugs, both rated high severity, earning him $2,000 in total. He also independently verified a third bug of high severity that had been found by Google.

Other bugs, meanwhile, involved "integer overflow in uniform arrays," buggy PDF memory handling in Chrome (Linux only), and various use after free errors.

All told, $8,000 in related bug bounties were paid out for nine bugs; two had been discovered by Google's own researchers. The current payout is less than the previous record of $17,000, which was paid out earlier this month for a prior release of Chrome.

Do bug bounties work? Google seems to think so. Based on the success of its cash-for-Chrome-flaws rewards program, Google last year extended the bug bounty program to cover any of its Web applications that handle sensitive user data.

Arguably, bug bounties socialize coordinated disclosure policies (previously known as "responsible disclosure") by giving security researchers incentives--cash, recognition--to help vendors patch bugs in their products.

Interestingly, Google's public disclosure of bugs discovered by its own employees isn't an industry standard practice. Notably, many vendors forego assigning a CVE identifier--referring to the widely used list of common vulnerabilities and exposures maintained by MITRE. According to the CVE website, the list "aims to provide common names for publicly known problems," in part to make it easier to share information about any given vulnerability.

In a blog post, Carsten Eiram, chief security specialist at vulnerability information provider Secunia, said that companies should always disclose bugs they've found, rather than performing a "silent fix," or in Microsoft-speak, treating it as a "variant," that gets patched but not detailed publicly.

"A software vendor should never silently fix vulnerabilities regardless of these being internally discovered or not; it is unethical and a disservice to customers," he said. "Vulnerability fixes should be clearly listed and, as such, become public and should be assigned a CVE identifier. Any public vulnerability should be assigned a CVE and all vulnerabilities should be made public."

He said that whenever MITRE becomes aware of a bug, it will assign it a CVE, regardless of whether or not the vendor has acknowledged the flaw. "This fact debunks the statement that there is no need for a software vendor to assign a CVE for an internally discovered vulnerability or similar," he said.

Eiram's comments came in response to a recent blog post from Brad Arkin, senior director of product security and privacy at Adobe. Arkin was responding to criticism that Adobe was undercounting the number of vulnerabilities discovered in its products. According to Arkin, "any bug identified by Adobe engineers and resolved as part of the Adobe Secure Product Lifecycle (SPLC) is not assigned a CVE."

At a full-day virtual event, InformationWeek and Dark Reading editors will talk with security experts about the causes and mistakes that lead to security breaches, both from the technology perspective and from the people perspective. It happens Aug. 25. Register now.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2015-03-02
The Crypto API in the Linux kernel before 3.18.5 allows local users to load arbitrary kernel modules via a bind system call for an AF_ALG socket with a module name in the salg_name field, a different vulnerability than CVE-2014-9644.

Published: 2015-03-02
net/netfilter/nf_conntrack_proto_generic.c in the Linux kernel before 3.18 generates incorrect conntrack entries during handling of certain iptables rule sets for the SCTP, DCCP, GRE, and UDP-Lite protocols, which allows remote attackers to bypass intended access restrictions via packets with disall...

Published: 2015-03-02
The Crypto API in the Linux kernel before 3.18.5 allows local users to load arbitrary kernel modules via a bind system call for an AF_ALG socket with a parenthesized module template expression in the salg_name field, as demonstrated by the vfat(aes) expression, a different vulnerability than CVE-201...

Published: 2015-03-02
The em_sysenter function in arch/x86/kvm/emulate.c in the Linux kernel before 3.18.5, when the guest OS lacks SYSENTER MSR initialization, allows guest OS users to gain guest OS privileges or cause a denial of service (guest OS crash) by triggering use of a 16-bit code segment for emulation of a SYS...

Published: 2015-03-01
The IBM Notes Traveler Companion application 1.0 and 1.1 before 201411010515 for Window Phone, as distributed in IBM Notes Traveler 9.0.1, does not properly restrict the number of executions of the automatic configuration option, which makes it easier for remote attackers to capture credentials by c...

Dark Reading Radio
Archived Dark Reading Radio
How can security professionals better engage with their peers, both in person and online? In this Dark Reading Radio show, we will talk to leaders at some of the security industry’s professional organizations about how security pros can get more involved – with their colleagues in the same industry, with their peers in other industries, and with the IT security community as a whole.