My next class:
Network Monitoring and Threat Detection In-DepthSingaporeNov 18th - Nov 23rd 2024

Flash Local-with-filesystem Sandbox Bypass

Published: 2011-01-06. Last Updated: 2011-01-06 04:52:41 UTC
by Johannes Ullrich (Version: 1)
2 comment(s)

Flash is designed around the "sandbox" concept to only allow access to specific local files, in particular of course flash cookie files. All other local files are off limits to Flash, to prevent malicious Flash applets from exfiltrating information.

Billy Rios, a researcher with some history when it comes to Flash, was able to show how to not only bypass this restriction and allow flash to access local files.

The local file access is amazingly simple: Adobe does allow access to remote files, via the "getURL" function. As pointed out by Billy, the easiest version of this attack would just use "file://" and point to the local system. However, Adobe blocklists certain protocol handlers, so Billy had to find one that was not blocklisted and would provided the access needed. One he found is the "mhtml" handler, which works on modern Windows systems, and is not blocklisted. The user will not be prompted for permission in this case.

http://xs-sniper.com/blog/2011/01/04/bypassing-flash%E2%80%99s-local-with-filesystem-sandbox/

------
Johannes B. Ullrich, Ph.D.
SANS Technology Institute
Twitter

Keywords: adobe flash
2 comment(s)
My next class:
Network Monitoring and Threat Detection In-DepthSingaporeNov 18th - Nov 23rd 2024

Comments

I can't resist pointing out that a sandbox should use _whitelists_ that list _acceptable_ protocols, not blacklists that doom you to playing whack-a-mole with exploits...

mhtml?
#insert obSuperciliousLinuxUserComment
I just read the linked story, and either I'm misunderstanding, or the writeup here seems to have the rights granted to the SWF in the PoC reversed.

There, it sounds more like the exploit prerequisite is having been granted local filesystem rights. The actual exploit isn't getting at those files, it's getting the data out. Flash is supposed to deny the SWF network access, preventing the SWF from sending what it finds on the local filesystem out. The exploit is using a non-blacklisted protocol handler to gain network access anyhow, thus allowing the SWF to send the contents of the local filesystem to a remote server.

Apologies if I misunderstand.

Diary Archives