Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by eridius on Thursday November 30, 2017 @07:46PM
(#15821054)
Wouldn't it make more sense just to fix the URL bar to make data URIs look different? You could even go to the extreme of making it just show "data:…" and requiring you to put focus on it to find out the full URI.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by userbinator on Thursday November 30, 2017 @10:06PM
(#15821604)
No kidding... this is a problem they created by hiding/obfuscating the URL scheme. If the majority of URLs you visit start with http:// or https://, then data: stands out like the proverbial sore thumb.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by beefhash on Thursday November 30, 2017 @11:51PM
(#15822010)
That requires that you know what you're doing, though. Non-technical people are probably more inclined to think along the lines of "huh, odd, but everything looks fine, so it's probably my fault it looks like that"
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by jchw on Friday December 01, 2017 @03:27AM
(#15822693)
Oh, I honestly would've missed this, because so few sites I browse are in cleartext anymore. They may as well just display a giant "INSECURE" banner, instead of http://, though.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by johnp_ on Friday December 01, 2017 @07:45AM
(#15823463)
FWIW, this recently landed in Firefox Nightly:
security.insecure_connection_icon.enabled
security.insecure_connection_icon.pbmode.enabled
Though it's still disabled by default (currently the insecure connection icon is only shown if a password field is present on a http page / the form action url is http).
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by discreditable on Thursday November 30, 2017 @03:53PM
(#15819417)
I'm glad they aren't blocking explicit entries. This morning I discovered I could quickly send snippets of text to my phone by writing it as a data uri and sending the tab via Fx sync.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by Mayzie on Thursday November 30, 2017 @11:46PM
(#15821982)
Alternatively for Android, you could enable KDE Connect[1] and copy the text to the clipboard (which will then be copied to the Android clipboard, and vice-versa). Or easily put it in a file and transfer it over to your device.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by muxator on Thursday November 30, 2017 @05:38PM
(#15820288)
I used to do exactly the same, but using a Firefox extension [0]. Since it is not compatible with quantum, I am writing my own, but it's still a prototype for now.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by dogma1138 on Thursday November 30, 2017 @04:16PM
(#15819613)
It is you can embed any binary in a b64 string in the html page and then download it from within the browser.
Since the download happens locally it also will not be logged in your perimeter monitoring and most security appliances do not inspect inline HTML especially from “trusted” domains due to performance limitation.
I’ve used this trick to bypass DLP, local policies and various content filtering appliances multiple times.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by tetromino_ on Thursday November 30, 2017 @05:37PM
(#15820280)
Depending on how exactly this block works, it may break an important functionality of our application :/
We generate SVG graphs in the browser, and have a button with a data:image/svg+xml URL to allow users to download these graphs, for example to include in a publication.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by tetromino_ on Thursday November 30, 2017 @06:35PM
(#15820659)
And that "I presume" instead of "I am quite certain" is precisely why I said I was worried about exactly how this block works. I will need to try with the beta, I suppose.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by rossy on Thursday November 30, 2017 @11:27PM
(#15821896)
Yeah, the form on http://sprunge.us/ is blocked for me in Firefox 58.0b7, which is kind of annoying because I used it regularly. If this is a phishing problem, couldn't it be fixed by changing UI rather than breaking functionality?
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by theandrewbailey on Thursday November 30, 2017 @04:55PM
(#15819929)
Hopefully data:image/ still works for favicons. Embedding a highly compressible ~450 byte string in HTML is faster than issuing a new request, under most instances.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by giancarlostoro on Thursday November 30, 2017 @05:39PM
(#15820296)
It does, not sure why you would think it doesn't? I do know chrome gets annoying about them, always requesting a sites favicon even when it doesn't have one listed in the document.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by tinus_hn on Thursday November 30, 2017 @05:58PM
(#15820435)
I haven’t seen them in the UI while I remember them being shown quite prominently. I wouldn’t really expect them to be used only for sites added to favorites because that’s a privacy issue.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by chriswarbo on Thursday November 30, 2017 @07:07PM
(#15820840)
Does anyone have a (non-malicious) example of this sort of "attack"? I don't quite get it; some people are mentioning Javascript, but the description sounds more like a phishing, e.g. `data:text/html;base64,MyBank.com/account/xxxxx`
Presumably such leading junk is hidden in the rendered page, making the user think they're on MyBank.com?
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by gruez on Thursday November 30, 2017 @07:17PM
(#15820906)
>Presumably such leading junk is hidden in the rendered page, making the user think they're on MyBank.com?
it's even simpler than that, they add a bunch of spaces after the "fake" url to pad out the actual payload so it doesn't show in the urlbar. any issues with the page content can be fixed with document.write or whatever.
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by Grollicus on Friday December 01, 2017 @05:37AM
(#15823087)
I know of a website that decrypts all its content clientside and uses this (i think) as a mechanism for a user to download his own attachments.
The Idea is that the whole website could be a static file somewhere and the webserver is only a key value store that has no idea what it is saving. Doesn't work that way currently because file:/// doesn't allow ajax calls to somewhere else but that's a solveable problem.
Generally, every download that gets generated clientside by the JS is hit by this
Re:Blocking Top-Level Navigations to Data URLs for Firefox 58
by DiThi on Thursday November 30, 2017 @06:22PM
(#15820583)
Only some bookmarklets that go to a data URL on top level are affected. They should be easy to modify to open them inside an iframe or to replace the existing document instead.
security.insecure_connection_icon.enabled
security.insecure_connection_icon.pbmode.enabled
Though it's still disabled by default (currently the insecure connection icon is only shown if a password field is present on a http page / the form action url is http).
[1] - https://community.kde.org/KDEConnect
[0] https://addons.mozilla.org/en-US/firefox/addon/offlineqr/
https://en.wikipedia.org/wiki/Encapsulated_PostScript
Since the download happens locally it also will not be logged in your perimeter monitoring and most security appliances do not inspect inline HTML especially from “trusted” domains due to performance limitation.
I’ve used this trick to bypass DLP, local policies and various content filtering appliances multiple times.
We generate SVG graphs in the browser, and have a button with a data:image/svg+xml URL to allow users to download these graphs, for example to include in a publication.
> Whereas the following cases will be allowed:
> • Downloading a data: URL, e.g. ‘save-link-as’ of “data:…”
I built a test to demonstrate: https://data-uri-test.glitch.me/
Presumably such leading junk is hidden in the rendered page, making the user think they're on MyBank.com?
The phishers are using a URL like `data:text/html,https://example.com/account/xxxxx (lots of spaces here) <script>/* phish phish phish */</script>`
You won't see that scary <script> in the URL unless your browser window is super-wide.
it's even simpler than that, they add a bunch of spaces after the "fake" url to pad out the actual payload so it doesn't show in the urlbar. any issues with the page content can be fixed with document.write or whatever.
The Idea is that the whole website could be a static file somewhere and the webserver is only a key value store that has no idea what it is saving. Doesn't work that way currently because file:/// doesn't allow ajax calls to somewhere else but that's a solveable problem.
Generally, every download that gets generated clientside by the JS is hit by this
Just curious-- why the exception for svg?
i.e.