4 ms·
At first you might think "why should Chrome protect people who forget to firewall their intranet?" but the real problem browsers are defending against is some p
by evmar 15y ago
At first you might think "why should Chrome protect people who forget to firewall their intranet?" but the real problem browsers are defending against is some page doing a million <img src='http://10.0.0.1:139> http://10.0.0.1:139> against an internal service that doesn't handle it well. (Or worse, a POST.)
(PS: HN shows extra characters than what I typed in that HTML. Might be an XSS vulnerability in there.)
- deleted 15y ago[deleted]
- jdukes 15y agoThis actually also has to do with cross protocol attacks. http://i8jesus.com/?p=75 http://i8jesus.com/?p=75
- maximusprime 15y agoThere was an attack last year on freenode which worked like this... javascript did an automatic POST to irc.freenode.net:6667 with form data that included IRC commands to spam channels etc. Unfortunately at the time their ircd didn't care about the 'POST / HTTP headers', and lovingly accepted the spam.