Google has patched a critical Chrome vulnerability disclosed last week at the CanSecWest security conference in Vancouver that can be exploited to escape from a browser’s secure sandbox.

Russian security researcher Sergey Glazunov demonstrated a remote code-execution (RCE) exploit against a fully patched version of Chrome on Windows 7 as part of Google’s Pwnium contest held at the conference..

Glazunov’s exploit leveraged two Chrome vulnerabilities – one that allows the execution of arbitrary code and one that bypasses the browser’s much-touted security sandbox, which normally restricts such exploits.

Remote code-execution vulnerabilities, while very serious, are relatively common in all software products. However, the sandbox escape ones are extremely rare and, according to TippingPoint, which runs the separate Pwn2Own contest at CanSecWest, are worth much more than the $60,000 Glazunov earned from Google for reporting it.

Both vulnerabilities leveraged by Glazunov’s exploit were fixed in Google Chrome 17.0.963.78, which was released on March 8.

“We had the first successful exploit at Pwnium, and today we’ve already rolling out an update to protect our users,” said Sundar Pichai, Google’s senior vice president for Chrome, on his Google+ account. “The team took less than 24 hours from initial report to verification to fix development to getting a fix out.”

Because of the Chrome’s auto-update feature, users just need to restart their browsers in order to deploy the security fix. Organisations can deploy the important update by using the Google Update for enterprise policy.

Glazunov’s was not the only Chrome sandbox escape exploit demoed at CanSecWest. A team of researchers from French security vendor VUPEN presented a similar attack as part of TippingPoint’ Pwn2Own contest.

However, the Pwn2Own rules don’t require researchers to disclose sandbox-escape vulnerabilities to vendors, primarily because the prize money wouldn’t justify their disclosure. This means that there is still one highly critical Chrome vulnerability out there that remains unpatched.

The Chrome security team suspects that it’s located in the Flash Player plug-in bundled with the browser by default and not in Chrome’s own code. There is no confirmation from VUPEN regarding this theory, but if true, the task of patching the vulnerability would fall with Adobe Systems.