Rolling out a sandbox for Adobe Flash Player

Wednesday, December 01, 2010

Since this past March, we’ve been working closely with Adobe to allow Flash Player to take advantage of new sandboxing technology in Chrome, extending the work we’ve already done with sandboxing for HTML rendering and JavaScript execution. This week, we’re excited to roll out the initial Flash Player sandbox for our dev channel users on Windows XP, Vista and 7.

This initial Flash Player sandbox is an important milestone in making Chrome even safer. In particular, users of Windows XP will see a major security benefit, as Chrome is currently the only browser on the XP platform that runs Flash Player in a sandbox. This first iteration of Chrome’s Flash Player sandbox for all Windows platforms uses a modified version of Chrome’s existing sandbox technology that protects certain sensitive resources from being accessed by malicious code, while allowing applications to use less sensitive ones. This implementation is a significant first step in further reducing the potential attack surface of the browser and protecting users against common malware.

While we’ve laid a tremendous amount of groundwork in this initial sandbox, there’s still more work to be done. We’re working to improve protection against additional attack vectors, and will be using this initial effort to provide fully sandboxed implementations of the Flash Player on all platforms.

We’ll be posting updates as we continue working with Adobe to add new security improvements to the Flash Player sandbox. For those of you on the dev channel for Windows, you’ll be automatically updated soon, and we look forward to your feedback as you test it out. If you prefer to disable this initial sandbox in your Chrome dev experience, add --disable-flash-sandbox to the command line.

12 comments:

The MAZZTer said...

Note that the sandbox breaks the flash Settings control panels, security exceptions (for controlling flash via javascript on local files), and flash file browse dialogs.

See http://crbug.com/64068

Artur Adib said...

Will this also lead to progress towards plugin compliance with @sandbox'ed iframes?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9851

Bassguy said...

Can't wait to test it on OS X.

Ciantic said...

Great! New dev channel is coming, I've been less than exhilarated with this 9.0.587.0 already.

But wasn't the command line flags thing of the past? I thought one can easily configure these experimental features from about:flags, I find it way handier.

TheBashar99 said...

While in theory this is good, in practice I've had a lot of problems with flash since the sandboxing of the plugin:
http://crbug.com/62905
http://crbug.com/63429

Sam said...

Can the sandbox keep flash audio under control too? Seems like it should need my permission before it can shit out of my speakers.

Ning Ning said...

I don't know much about programming, and couldn't find an appropriate place to post this, but in the next Google Chrome browser release, could pressing Ctrl+F once, opening up the "find" feature, then pressing again close the "find" feature? Thanks.

mahmojud said...

very nice post

thanxxxxxxxxxx


http://itstate.blogspot.com/

none said...

I have more than a year using a sandbox for flash with thinapp :P

SethB said...

Doesn't the --safe-plugins switch sandbox all plugins, including Flash? How does the sandbox achieved with that switch differ from this new sandbox for the Flash plugin?

Sareezfashions said...

We have a huge collection of designer clothes like Sarees, Salwar Kameez and Lehenga Cholis visit - http://www.sareez.com/

Jack Hsu said...

Nice, but if you use the TAPDrive, you won't have to worry about "sandboxing" anything.

http://www.tapdrive.com