Google's trap for Chrome exploit writers leads to crashes for users
Flash exploit mitigation recently built into Chrome caused more problems than it solved
IDG News Service - A limitation built recently into Google Chrome to detect and block Flash Player exploits ended up breaking certain Flash-based applications and games for some users.
Suspecting that someone would try to hack Chrome via a Flash exploit at this year's Pwn2Own contest, the browser's developers decided to restrict the maximum allowed size of Flash JIT (just-in-time) pages to a value that such exploits would likely exceed.
The restriction was written in such a way that when the new limit would be reached the browser would throw an "access violation" exception that referenced memory address "0xABAD1DEA," a hexadecimal value spelling out "a bad idea."
According to Chrome's development tracker, the limit was introduced on Feb. 23 and was first tested out in the browser's Canary (nightly build) version. The limit was later tweaked because of a considerable number of crash reports and landed in Chrome stable version 17.0.963.66 on Mar. 6.
Some of the Pwn2Own contestants did stumble over the Flash JIT page restriction. Nicolas Joly, a member of the VUPEN Security team, which eventually won the hacking contest, said on Twitter that he encountered 0xABAD1DEA exceptions during his tests.
Google Chrome security engineer Justin Schuh revealed that he was the one who put it there in order to detect Flash exploits. "0xABAD1DEA was a breadcrumb I added that's unique to Flash," he said on Twitter.
Schuh later clarified that it wasn't just a trap, but also a mitigation, although he admitted that it was a weak one. The VUPEN Team eventually managed to work their way around the restriction and hacked Chrome during the contest.
However, Google's half-mitigation, half-trap code caused more problems than it solved, because it ended up interfering with the normal operation of some legitimate Flash-based applications and games, like Sims Social, Audiotool and Paychex Online.
According to reports on the Google Chrome support forum, users started experiencing Flash Player crashes referencing 0xABAD1DEA after they upgraded to Chrome version 17.0.963.66.
Changes aimed at addressing the problem were made in Chrome version 17.0.963.79, which was released on Saturday, a Google employee said in response to the reports. However, some users still experienced 0xABAD1DEA-related crashes after upgrading to it.
- 15 Non-Certified IT Skills Growing in Demand
- How 19 Tech Titans Target Healthcare
- Twitter Suffering From Growing Pains (and Facebook Comparisons)
- Agile Comes to Data Integration
- Slideshow: 7 security mistakes people make with their mobile device
- iOS vs. Android: Which is more secure?
- 11 sure signs you've been hacked
- The Threat Landscape Hardly a day goes by without the discovery of a new cyberthreat somewhere in the world! But how do you keep up with...
- Security for Virtualization In the rush to implement virtualization, security has become second. So while the business benefits are clear, the risks are less well documented...
- Pay-as-you-Grow Data Protection: IBM Tivoli's Full-featured Data Protection Suite for Small to Medium Businesses IBM Tivoli Storage Manager Suite for Unified Recovery gives small and medium businesses the opportunity to start out with only the individual solutions...
- Streamline Data Protection with IBM Tivoli Storage Manager Operations Center IBM Tivoli Storage Manager (TSM) has been an industry-standard data protection solution for two decades. But, where most competitors focus exclusively on Backup...
- Meg Whitman presents Unlocking IT with Big Data During this Web Event you will hear Meg Whitman, President and CEO, HP discuss HAVEn - the #1 Big Data platform, as well...
- The New Way to Work Knowledge Vault This Knowledge Vault focuses on how, in today's increasingly virtual world, it's more important than ever to engage deeply with employees, suppliers, partners,... All Malware and Vulnerabilities White Papers | Webcasts