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.
[ Parent
| on HN ]
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...