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

2/28/2012
02:14 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Google Offers $1 Million For Chrome Hacks

Google prepares to open its wallet for reports of security flaws, but outside annual Pwn2Own hacker competition.

Google has raised the total amount it will pay for Chrome security flaws by a factor of fifty compared to last year, but it is doing so outside of the Pwn2Own hacking competition.

In 2011, Google promised up to $20,000 in rewards for Chrome browser exploits at the CanSecWest security conference, where HP TippingPoint's Pwn2Own hacking competition is held.

Pwn2Own is a competition in which computer security experts attempt to compromise operating systems and Web browsers using bugs that they've identified.

This year, Google says it will pay out as much as $1 million in reward money. Hackers however will have to reveal quite a few exploitable bugs to win that much: Google will pay at most $60,000 for any single "full Chrome exploit."

But even Google's consolation prize--$20,000 for the identification of flaws in non-Chrome software like Flash or Windows--is as much as the total reward purse put forth by the company last year.

[ What happened at Pwn2Own last year? Read Safari, IE Defeated, Chrome, Firefox Survive. ]

Google is offering the money through its two-year-old Chromium Security Rewards program, which has paid out over $300,000 during its brief lifetime.

This year, Google has decided not to support Pwn2Own because the contest rules do not require full disclosure of the exploit.

"Full exploits have been handed over in previous years, but it's an explicit non-requirement in this year's contest, and that's worrisome," said Chris Evans and Justin Schuh, members of Google's Chrome security team, in a blog post. "We will therefore be running this alternative Chrome-specific reward program."

Pwn2Own will run as usual, without Google's sponsorship, from March 7th through March 9th. Hackers will have the option to attack any of the four major browsers--Apple Safari, Google Chrome, Microsoft Internet Explorer, and Mozilla Firefox--on fully patched versions of either Windows 7 or OS X Lion.

The top three winners will be awarded $60,000, $30,000, and $15,000 respectively from HP, and each will have the option of choosing one laptop from a group of three: an Asus Zenbook UX31 with a Core i7 CPU and 256-GB SSD, an Asus Zenbook UX21 with a Core i7 CPU and 256-GB SSD, or a Macbook Air 11" with a Core i7 CPU and 256-GB SSD.

There is a catch worth noting: Exploits must be submitted to and evaluated by Google first, before they are submitted elsewhere.

To protect company and customer data, we need to determine what makes it so vulnerable and appealing. We also need to understand how hackers operate, and what tools and processes they rely on. In our How (And Why) Attackers Choose Their Targets report, we explain how to ensure the best defense by thinking like an attacker and identifying the weakest link in your own corporate data chain. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Sabrina
50%
50%
Sabrina,
User Rank: Apprentice
3/1/2012 | 7:01:11 AM
re: Google Offers $1 Million For Chrome Hacks
Gogole supports Chrome so it tends to do it
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/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-26120
PUBLISHED: 2020-09-27
XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even witho...
CVE-2020-26121
PUBLISHED: 2020-09-27
An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an uploa...
CVE-2020-25812
PUBLISHED: 2020-09-27
An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML.
CVE-2020-25813
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users.
CVE-2020-25814
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> ...