Re:Abusing Protocols to Load Local Files, Bypass the HTML5 S...
by Klathmon on Saturday November 26, 2016 @07:35PM
(#13046949)
Even (b) is pushing IMO. There's a reason the standards have evolved to be this restrictive. If you want to allow a way to get around those restrictions (with "you" being a browser vendor), then you should go through the standardization process.
9/10 these "good intentioned" additions to browsers end up being used in exploits, and even if they aren't just being in one browser is rarely useful.
Re:Abusing Protocols to Load Local Files, Bypass the HTML5 S...
by dvt on Saturday November 26, 2016 @09:14PM
(#13047313)
Yep, totally agree. The exploiting potential far outweighs the usefulness.
Re:Abusing Protocols to Load Local Files, Bypass the HTML5 S...
by crazy2be on Saturday November 26, 2016 @09:39PM
(#13047388)
I don't know, I can't see any way that the read: protocol is any more vulnerable than the file: protocol (standard on all browsers), other than the fact that the code is probably less battle-tested.
Re:Abusing Protocols to Load Local Files, Bypass the HTML5 S...
by userbinator on Saturday November 26, 2016 @10:44PM
(#13047568)
The part of the string before the comma may do something interesting; further reverse-engineering may reveal its purpose, but what I'd like to know more is what application(s) actually use read: and for what.
Re:Abusing Protocols to Load Local Files, Bypass the HTML5 S...
by kalleboo on Sunday November 27, 2016 @08:37AM
(#13049048)
From the function names in the stack trace, I assume it's the internal protocol used for "Reading View" https://support.microsoft.com/en-us/help/17204/windows-10-ta...
Re:Abusing Protocols to Load Local Files, Bypass the HTML5 S...
by userbinator on Sunday November 27, 2016 @11:29AM
(#13049945)
That somewhat makes sense, but then one wonders why it wasn't restricted in the same way as file:// or the usual http(s):// protocols. Of course "Reading View" could've been implemented in a simpler way that people were accomplishing the same thing before (either saving the pages or their URLs to a centralised place), but leave it to MS to reinvent it in the form of an overly complex and insecure solution...
However, the fact that the "read:" protocol is a thing -- and the fact that it works the way it works -- is absolutely insane. Who in their right mind would think that's a good idea? Forget sandboxing, who's bright idea was it to let a web browser access local files willy-nilly? Mind-boggling.
The first thing I'd say if someone came to me with that idea is (a) no way and (b) if you really want to do it, you need a security mechanism like 300x stronger than CORS and probably a popup that lets the user know what's going on.