Wiccle.com in Facebook Wiccle.com in Twitter Wiccle.com in LinkedIn Wiccle.com in Youtube RSS from Wiccle.com Wiccle.com in Atom
 
 
 

Thread: Adobe Flash uploader security risk/hole

Started: November 14, 2009, 01:42 AM  ⋅  Zone: Public Forums  ⋅  Category: General Chat  ⋅  Posts: 8  ⋅  Views 16024
Started by: Footman  ⋅  Description: No description.
Post #1
Member: Footman  ⋅  Date: November 14, 2009, 01:42 AM  ⋅ Subject: "Adobe Flash uploader security risk/hole"

I saw this link on another board and thought it might be worth chatting about here. What I gather from the article the only way to ensure saome measure of safety here, other than not using flash, is to host any members uploaded images/files on another domain seperate from the main site. The I suppose they're pulled from that domain ala hotlinking. Is that correct? If so, I'd love to know how to do this OR is it really as bad/inevitable as they make it sound?

http://www.computerworld.com/s/article/9140768/Flash_flaw_puts_most_sites_users_at_risk_say_researchers

Post #2
Member: Markus  ⋅  Date: November 14, 2009, 03:26 PM  ⋅ Subject: "Re: Adobe Flash uploader security risk/hole"

Thanks for posting this. I have, for many reasons (ask for a list Laughing), been avoiding the use of Flash wherever possible for a while now. While it's a useful invention, it's often used in places where AJAX and a bit of javascripting would do.

The article is a bit ambiguous on how exactly the exploit happens. Flash exploits targeted from browser to the end-user's computer have been around for some time now --- and because you can stick just about anything into a flash object (and as others can't see the source) it makes it all the more easy, and because you can also embed Flash objects from third-party sites to a page, it's even more easy.

What I am concerned over is whether this can be employed for server-targeted attacks, for example by using the uploaded flash object to piggyback malicious code into public-writable folders on the server's file system. In fact, now that you mention, I have a couple of ideas how one might accomplish just that... I need to look into this a bit deeper, and consider a flash-freeze policy after I get to review the specifications for how these newly hyped exploits work.

If anyone finds links to articles that go into more technical detail on this, I'd appreciate if you shared them with me. I read through the more technical bit linked to from the article, but it still doesn't really get into sufficient detail to allow analyzing and addressing the issue.

Post #3
Member: Markus  ⋅  Date: November 15, 2009, 03:36 PM  ⋅ Subject: "Re: Adobe Flash uploader security risk/hole"

I should probably implement an optional upload-domain-isolation into our next release as well. It was originally a part of the roadmap for when we begin working on clustered servers and high-end scalability, but I suppose this issue is serious enough to merit a change in plans. What say the public?

Post #4
Member: Footman  ⋅  Date: November 15, 2009, 04:17 PM  ⋅ Subject: "Re: Adobe Flash uploader security risk/hole"

I assume that mean user uploads will be stored somewhere other than the main domain so as to minimize any possible attacks via flash. Then those files/images/vids etc will be drawn from there to the main domain page which is calling for them.

I vote yes Cool

Post #5
Member: Markus  ⋅  Date: November 15, 2009, 05:13 PM  ⋅ Subject: "Re: Adobe Flash uploader security risk/hole"

Yes exactly, that's what it means. =) It's something I have been meaning to do for a while at our own site here for general isolation purposes, so we might as well roll it out to everyone as an option.

Post #6
Member: Footman  ⋅  Date: November 15, 2009, 06:16 PM  ⋅ Subject: "Re: Adobe Flash uploader security risk/hole"

would a sub-domain work well for this or is it advisable to have a whole seperate TLD? Will this slow the loading of the files to the main site?

Post #7
Member: Markus  ⋅  Date: November 15, 2009, 08:39 PM  ⋅ Subject: "Re: Adobe Flash uploader security risk/hole"

From what I read, subdomains are also vulnerable, at least in some situations. I'll write more on this when I get a moment to study this in a bit more detail. This will also affect our entire setup here, and we do like to keep things as secure as possible (gateways and license database are already under a separate TLD and isolated), so rest assured we'll do our best to get it to the best possible shape.

Thanks again for posting this topic, and feel free to continue along the same lines! You and other members can set up blogs if you want (we'd welcome that very much), and open topics like this with good introductions, as you have done here. Smile

Post #8
Member: Footman  ⋅  Date: November 16, 2009, 05:56 PM  ⋅ Subject: "Re: Adobe Flash uploader security risk/hole"

it's a blog topic now Cool

Should be interesting to see the outcome of this.

 

General Chat

Add to Favorites
Public Forums
Category  ⋅  On and off topic, almost anything goes, but let's keep it civil and reasonable.
 

Public Forums

Add to Favorites
Public Forums
Zone  ⋅ Public forum sections for support and discussions. Available for everyone.
 

Zone Categories

 
Questions? Ask us!
Back to Top