Google Pwnium hacking contest prize fund increased to $3.14 million

New cooperative approach with Pwn2Own has Google pitching researchers on hacking Chrome OS

Article comments

Google has announced it would again host its Pwnium hacking contest at a March security conference, but boosted the maximum amount it will pay to $3.14 million and changed the target to its browser-based operating system, Chrome OS.

Dubbed Pwnium 3, the challenge will pit researchers against its still-struggling-for-relevance Chrome OS, rewarding those who can hack the operating system with individual prizes of $110,000 and $150,000.

Google capped the total up for grabs at $3,141,590, giving multiple researchers a chance at prize money. The "3.14159" comes from the first six digits of the value of Pi.

Each hacker able to compromise Chrome OS or the browser that is its foundation - Chrome - from an exploit-serving website will receive $110,000 said Chris Evans, an engineer with the Chrome security team.

Researchers who manage to accomplish what Evans called a "compromise with device persistence," meaning that the hijack survives a reboot of the Chrome OS-powered notebook, will receive the larger award of $150,000.

"We believe these larger rewards reflect the additional challenge involved with tackling the security defences of Chrome OS, compared to traditional operating systems," said Evans.

Pwnium 3 will take place March 7 at CanSecWest, the Vancouver, British Columbia, security conference where Google will also partner with HP TippingPoint's Zero Day Initiative (ZDI) bug bounty program to host Pwn2Own. That contest, with $560,000 in total cash prizes, will focus on web browsers, including Chrome, Microsoft's Internet Explorer (IE) and Mozilla's Firefox, as well as plug-ins from Adobe and Oracle.

The contest cooperation at CanSecWest will be quite different this year than in 2012, when Pwn2Own and Pwnium were rivals. Google inaugurated Pwnium then after it withdrew its financial support from Pwn2Own after it and HP couldn't agree on the rules - specifically, whether researchers would be required to divulge full exploits and hand over all the vulnerabilities they used to hack a browser.

"This year, we've teamed up with ZDI by working together on the Pwn2Own rules and by underwriting a portion of the winnings for all targets," said Evans about the new understanding between Google and HP TippingPoint. "The new rules are designed to enable a contest that significantly improves internet security for everyone. At the same time, the best researchers in the industry get to showcase their skills and take home some generous rewards."

Both Pwn2Own and Pwnium will require winners to provide functional exploit code and details on all the vulnerabilities put into play.

Pwnium 3's $3.14 million cap is more than three times the $1 million Google said it would pay if necessary in 2012, and more than 50% above the $2 million it staked at a second challenge that took place in Kuala Lumpur, Malaysia, last October.

But if past practice holds true again this year, Google won't write checks totaling anywhere near $3 million. At the first Pwnium of March 2012, the search giant paid out $120,000 to two researchers for exploiting Chrome; the Malaysian edition's single award was a $60,000 payoff to "Pinkie Pie," one of the two hackers who took home the same amount seven months earlier.

Chrome OS has never been a contest target before, although Pwn2Own offered a Chrome OS notebook as one of four laptop prizes in 2011.

Google has not yet posted the official rules for Pwnium 3, but they will probably appear on the Chromium Security page.


Send to a friend

Email this article to a friend or colleague:

PLEASE NOTE: Your name is used only to let the recipient know who sent the story, and in case of transmission error. Both your name and the recipient's name and address will not be used for any other purpose.

We use cookies to provide you with a better experience. If you continue to use this site, we'll assume you're happy with this. Alternatively, click here to find out how to manage these cookies

hide cookie message
* *