Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

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.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/9/2020
Introducing 'Secure Access Service Edge'
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  7/3/2020
Russian Cyber Gang 'Cosmic Lynx' Focuses on Email Fraud
Kelly Sheridan, Staff Editor, Dark Reading,  7/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15001
PUBLISHED: 2020-07-09
An information leak was discovered on Yubico YubiKey 5 NFC devices 5.0.0 to 5.2.6 and 5.3.0 to 5.3.1. The OTP application allows a user to set optional access codes on OTP slots. This access code is intended to prevent unauthorized changes to OTP configurations. The access code is not checked when u...
CVE-2020-15092
PUBLISHED: 2020-07-09
In TimelineJS before version 3.7.0, some user data renders as HTML. An attacker could implement an XSS exploit with maliciously crafted content in a number of data fields. This risk is present whether the source data for the timeline is stored on Google Sheets or in a JSON configuration file. Most T...
CVE-2020-15093
PUBLISHED: 2020-07-09
The tough library (Rust/crates.io) prior to version 0.7.1 does not properly verify the threshold of cryptographic signatures. It allows an attacker to duplicate a valid signature in order to circumvent TUF requiring a minimum threshold of unique signatures before the metadata is considered valid. A ...
CVE-2020-15299
PUBLISHED: 2020-07-09
A reflected Cross-Site Scripting (XSS) Vulnerability in the KingComposer plugin through 2.9.4 for WordPress allows remote attackers to trick a victim into submitting an install_online_preset AJAX request containing base64-encoded JavaScript (in the kc-online-preset-data POST parameter) that is execu...
CVE-2020-4173
PUBLISHED: 2020-07-09
IBM Guardium Activity Insights 10.6 and 11.0 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure l...