Microsoft Edge Lets Facebook Run Flash Code Behind Users' Backs (zdnet.com)
An anonymous reader writes: Microsoft's Edge browser contains a secret whitelist that lets Facebook run Adobe Flash code behind users' backs. The whitelist allows Facebook's Flash content to bypass Edge security features such as the click-to-play policy that normally prevents websites from running Flash code without user approval beforehand.
The whitelist isn't new. It existed in Edge before, and prior to February 2018, it included 58 entries, including domains and subdomains for Microsoft's main site, the MSN portal, music streaming service Deezer, Yahoo, and Chinese social network QQ. The list was narrowed down to only two Facebook domains (facebook.com and apps.facebook.com) after a Google security researcher found that the whitelist mechanism had some security issues. The bug report also contains the original version of the whitelist, with all the 58 domains.
The whitelist isn't new. It existed in Edge before, and prior to February 2018, it included 58 entries, including domains and subdomains for Microsoft's main site, the MSN portal, music streaming service Deezer, Yahoo, and Chinese social network QQ. The list was narrowed down to only two Facebook domains (facebook.com and apps.facebook.com) after a Google security researcher found that the whitelist mechanism had some security issues. The bug report also contains the original version of the whitelist, with all the 58 domains.
An oxymoron if I ever saw one.
Except for a fast lane, big companies are bypassing necessary security blocks to "trusted" (aka paying) sites.
These free passes are really an issue on the open web. As it means Facebook can have features enabled that other sites may not (at least without a warning).
As doing web development, when I see something interesting, I will dig into the code to figure it out. Like how Google gave the search suggestions while typing, and Google Maps a while back, that is where I learned Ajax. But if all the major browser makers, just made a <GoogleSearchAhead> tag If I were to try to make something based on the technology, it would be blocked to me.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
He probably gave up on the internet :)
The funny thing is that after MS tortured everyone with IE, even if Edge was amazing, most of us wouldn't even give it a chance.
(sorry)
And yet again no one listens. I expect Mozilla and Google have "secret lists" too. Brave was recently exposed sending "secret headers" to certain websites too.
I mean, come on, the fact they encrypted the list and it had to be brute-forced meant that a) Microsoft didn't want us know and b) they knew it was sneaky. How much more anti-consumer can a program be -- it was hiding intentional violations of its own touted 'security policies' for some privileged group that isn't the user.
In the transition time to deprecating Flash and removing it from browsers entirely, there are still sites that use Flash and users of those sites which rely on it. So, all of the browsers have a whitelist which allows some sites to continue working while preventing others from introducing brand-new Flash content. This helps with the transition. Eventually the browsers narrow this list down in scope and add more security barriers in front of Flash until they can remove it entirely. That sounds exactly like what is happening here; the whitelist is down to two entries both of which are extremely popular sites. The whitelist and Flash itself will likely be removed at some point. I am not sure why the cause for alarm here; it wasn't too long ago that flash ran by default on ALL websites.
I think the only real point of concern here is the lack of click to play, especially since anyone can make a Flash app with who knows what spyware as content and get it uploaded as a Facebook app.
And you know this because you have carefully examined every line of source code, right?
> Don't use Edge and Facebook blocked in hosts file
What is hosts file and how do you block things in it?
All you need to do is redirect your "WiFi login" page to a whitelisted domain, MITM that domain, since you control the wifi network, and deliver what ever malicious Flash content you desire.
Easy to do, since the whitelist is not restricted to HTTPS connections.
As pointed out earlier by another poster, that's getting harder and harder as well.
More programs *cough*Chrome*cough* are using their own internal resolvers instead of the system one, and running those over HTTPS specifically to bypass local domain blocks. IP blocks are also difficult with today's CDNs with large numbers of ever changing IPs, and domain based virtual hosts.
Sure, you can get around all this for now, but I'm not sure that long term you'll be able to.
Which has supported Flash since 1996
Navigator? c'mon, real men use lynx!
Emacs M-x browse-web
How many Edge users were upset to learn about the secret whitelist that allows Facebook to run Flash?
Both!
As even Apple has learned. Now Microsoft will be burned.
Corporatism != Free Market
and vsphere mgmt.
NCSA Mosaic.
Have gnu, will travel.
Hey Wiretap, what is a good recipe for Chocolate Cake?
Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
Other than as the world's most popular method of downloading Chrome...
I've abandoned my search for truth; now I'm just looking for some useful delusions.
Chrome does DNS query caching; it doesnâ(TM)t have its own DNS it consults.
But I came here for an argument!
Nothing nefarious here, just good ol' Microsoft secretly fucking over you and your PC behind your back.
I will say this is different; usually they do it right to your face.
So glad I switched to Mint, not that I ever would have allowed Edge* to run. The ONLY thing Edge might be good for is downloading another browser, beyond that it's pure rubbish.
.
*Edge, AKA "The Little Browser That Couldn't"
Just cruising through this digital world at 33 1/3 rpm...
...and compiled it yourself?
Yes, and I wrote the compiler and fabricated the integrated circuits myself.
Just cruising through this digital world at 33 1/3 rpm...
expect the same tricks from the MS chrome based browser, another reason just to not use it.
changing rendering engines will not make me change my mind.
On a long enough timeline, the survival rate for everyone drops to zero.
After investigating, it looks like Google backtracked on it, and removed the async dns resolver a little while ago (here's a post that talks about what it was: https://discourse.pi-hole.net/t/disable-async-dns-resolver-in-google-chrome/9500)
So yes, Chrome DID have it's own internal resolver, but they seem to have backtracked and now only have a cache (which still will cause problems if you're switching between servers such as internal corporate DNS to outside world when you connect/disconnect your company VPN).
That said other apps (especially mobile games) have been caught with their own internal resolvers so as to ensure no adblocker (or malware blocker) can be used.