3 ms·
Whatever that website is, has an issue, since that backup.tar may contain their database credentials. The favicon thing is just an annoying browser crashing bu
by Someone1234 11y ago
Whatever that website is, has an issue, since that backup.tar may contain their database credentials.
The favicon thing is just an annoying browser crashing bug. You could call that an "exploit" but up until fairly recently you were able to crash many browsers by generating too many message boxes (e.g. alert()) asynchronously.
So while, yes, it would be nice to fix it I don't really see it as being a high priority or one which will be actively exploited (since there is no "payoff" to either prankers or bad guys to this exploit).
- inglor 11y agoEating users' bandwidth has its uses as well as filling up a network with communication. This works with JavaScript disabled too but yeah I agree it's not a huge priority.
- rlemon 11y agoI know for a fact that eating mobile bandwidth would be a huge priority for some (as far as getting it fixed). For example; I live in Canada and my mobile plan is only for 8gb. If I go over I have to pay a premium, and it is not a cheap premium. I don't think unlimited bandwidth on mobile is popular (at least here, I suspect other places cough India cough) as well.
- Someone1234 11y agoEven if you cap favicon size you don't solve the issue you're discussing at all. A bad actor web-site can just move from favicon to an image, script file, or just return an indefinite series of HTML characters with no end. The only way for the issue you want solved to be solved is for mobile browsers to add a "max page size" option, that will stop downloading content after it hits the cap. In general this favicon bug is neither here nor there with the issue you're concerned about. Nobody needs this to waste your bandwidth. The only reason this is noteworthy is that it is a little embarrassing for the browser vendors and it causes the browsers (Firefox and Chrome) to crash.