Google patches WebKit flaw after Pwn2Own contest

Powered by SC Magazine
 

Rewards hack team.

Google has patched a vulnerability exploited by researchers at last week’s Pwn2Own hacking contest.

Even though Google Chrome was not hacked during the competition, the bug resided in WebKit - the rendering engine used by the browser.

WebKit is also featured in Apple’s Safari and the browser found on BlackBerry phones.

A team of researchers, including Willem Pinckaers, Vincenzo Iozzo and Ralf-Philipp Weinmann, hacked a BlackBerry Torch 9800 by exploiting the vulnerability.

On top of the US$15,000 they received for the BlackBerry hack, the researchers were handed US$1,337 from Google.

The update, in Google Chrome 10.0.648.133, only fixed the WebKit security issue.

The memory corruption bug was given a high priority ranking, but Google was not forthcoming on any additional details.

”Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix,” said Jason Kersey, from the Google Chrome team.

Google has handed out over US$100,000 as part of its Chromium Security Rewards programme.

This article originally appeared at itpro.co.uk

Copyright © ITPro, Dennis Publishing


Google patches WebKit flaw after Pwn2Own contest
 
Readers of this article also read...
 
 
Top Stories
The True Cost of BYOD - 2014 survey
Twelve months on from our first study, is BYOD a better proposition?
 
Photos: Unboxing the Magnus supercomputer
Pawsey's biggest beast slots into place.
 
ANZ looks to life beyond the transaction
If digital disruptors think an online payments startup could rock the big four, they’ve missed the point of why people use banks, says Patrick Maes.
 
 
Sign up to receive iTnews email bulletins
   FOLLOW US...
Latest Comments
Polls
What is delaying adoption of public cloud in your organisation?







   |   View results
Lock-in concerns
  29%
 
Application integration concerns
  3%
 
Security and compliance concerns
  28%
 
Unreliable network infrastructure
  9%
 
Data sovereignty concerns
  21%
 
Lack of stakeholder support
  3%
 
Protecting on-premise IT jobs
  4%
 
Difficulty transitioning CapEx budget into OpEx
  3%
TOTAL VOTES: 1088

Vote