4 ms·
Hm.. So a simple javascript that loads the image from specified path would hang M$ windows? Applicable to html emails too in some mail client? We need to find
by pksadiq 9y ago
Hm.. So a simple javascript that loads the image from specified path would hang M$ windows? Applicable to html emails too in some mail client?
We need to find more astonishing ways to hang the windows. Cement and sand should not be the only option.
- jordache 9y agobrowsers implement cross domain origin policy to prevent js from accessing the local filesystem. Or did I misunderstand the nature of the Windows bug. It must be trying to read from file:// right?
- komali2 9y ago<img src="c://badfilename"> is enough. You don't need JavaScript.
- jordache 9y agois this true for even evergreen browsers? Is this true for pages that's hosted in non localhost domain or drag n' dropped into browser from the file explorer? (file:// protocol)
- deelowe 9y agoBut you do need the file to be stored locally. I don't think this attack is very serious. Downloading and opening files is already a risky maneuver.
- komali2 9y agoMy understanding of the article is there isn't a "local file" that matches the name, but the very act of checking for that filename causes the hang. Happy to be corrected.
- tbodt 9y agoheaven praise the same origin policy
- blockoperation 9y agoResources/frames/XHRs/etc from 'file://' might be blocked, but what about top-level redirects? At the very least, user-initiated top-level navigations should bypass any policies. If you're out to cause mischief, you could just link to the dodgy path on forums/comments/etc – there'll always be people out there who are careless and/or clueless enough to click on it.