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.

Risk

1/29/2010
04:29 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Google Offers Hackers Bucks For Chrome Bugs

New vulnerability disclosure incentive program pays a minimum $500 per critical bug

Google is now offering hackers money for discovering vulnerabilities in its Chrome browser -- a practice already in place at Mozilla.

The experimental incentive program is meant to entice researchers outside of the Chromium project to provide security feedback for the browser. Google says it will pay $500 for an eligible bug discovery and $1,337 for an especially severe or clever vulnerability; a single bug could be considered as multiple vulnerabilities.

"The more people involved in scrutinizing Chromium's code and behavior, the more secure our millions of users will be," said Chris Evans, Google Chrome Security, in a blog post today announcing the new program.

Google credited Mozilla for the idea of offering rewards for vulnerability finds in its software.

Chrome security has been on the front burner for Google this week. The search engine giant on Monday issued an update to Chrome that included security fixes and new features, including stronger transport security and a cross-site scripting (XSS) protection feature.

But the practice of offering bug bounties traditionally has been controversial, with opponents saying it sends the wrong message and supporters saying researchers should receive compensation for their efforts in helping vendors pinpoint holes. Companies such as TippingPoint's ZDI and iDefense have paid outside researchers for their finds for some time.

But some experts argue it can backfire because the black market pays more for vulnerability discoveries.

"Acknowledging there's a commercial market for flaws is also acknowledging that you're leaving open the possibility that someone is going to make a lot more money in the dark markets," says Joshua Corman, research director for the enterprise security practice at The 451 Group. "The idea is that you want to encourage researchers to proactively beat up your software so you can fix it before it's exploited by the bad guys. That's a great idea. But the wrinkle is that you're planting a seed that otherwise might not have been there, that, 'I might make money on this.'"

And these bug incentive programs don't prevent zero-day vulnerability discoveries from nonparticipants, he says.

Google says bugs just in Chrome or in the overall Chromium open-source project are eligible for the incentive program, but not vulnerabilities in third-party plug-ins.

"We encourage responsible disclosure. Note that we believe responsible disclosure is a two-way street; it's our job to fix serious bugs within a reasonable time frame," Evans said.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message. Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/27/2020
Chinese Attackers' Favorite Flaws Prove Global Threats, Research Shows
Kelly Sheridan, Staff Editor, Dark Reading,  10/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11484
PUBLISHED: 2020-10-29
NVIDIA DGX servers, all DGX-1 with BMC firmware versions prior to 3.38.30, contains a vulnerability in the AMI BMC firmware in which an attacker with administrative privileges can obtain the hash of the BMC/IPMI user password, which may lead to information disclosure.
CVE-2020-11485
PUBLISHED: 2020-10-29
NVIDIA DGX servers, all DGX-1 with BMC firmware versions prior to 3.38.30, contains a Cross-Site Request Forgery (CSRF) vulnerability in the AMI BMC firmware in which the web application does not sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the u...
CVE-2020-11486
PUBLISHED: 2020-10-29
NVIDIA DGX servers, all DGX-1 with BMC firmware versions prior to 3.38.30, contain a vulnerability in the AMI BMC firmware in which software allows an attacker to upload or transfer files that can be automatically processed within the product's environment, which may lead to remote code execution.
CVE-2020-11487
PUBLISHED: 2020-10-29
NVIDIA DGX servers, DGX-1 with BMC firmware versions prior to 3.38.30. DGX-2 with BMC firmware versions prior to 1.06.06 and all DGX A100 Servers with all BMC firmware versions, contains a vulnerability in the AMI BMC firmware in which the use of a hard-coded RSA 1024 key with weak ciphers may lead ...
CVE-2020-11488
PUBLISHED: 2020-10-29
NVIDIA DGX servers, all DGX-1 with BMC firmware versions prior to 3.38.30 and all DGX-2 with BMC firmware versions prior to 1.06.06, contains a vulnerability in the AMI BMC firmware in which software does not validate the RSA 1024 public key used to verify the firmware signature, which may lead to i...