3 ms·
One website can use resources from other website using img, script, link tags. That was since WWW invented. User agent will retrieve related resources from othe
by vbezhenar 6y ago
One website can use resources from other website using img, script, link tags. That was since WWW invented. User agent will retrieve related resources from other websites.
Those port scanners abuse that feature. <img href="https://website-resolving-to-127-0-0-1.com:1234"> https://website-resolving-to-127-0-0-1.com:1234"> is a legitimate code and browser is expect to establish TLS connection to 127.0.0.1:1234.
Trying to patch that fundamental behaviour is hard.
Websockets are not enemy here. They are just convenient tool. It could be implemented without websockets.
Imagine that google.com added <img src=yourpoorwebsite.com> into their main page. Now you've got billions of requests and your website is DDoSed. Who's bad here? Browser which allows requests from google.com to yourpoorwebsite.com? Or Google who decided to kill your website?
- cygx 6y agoTrying to patch that fundamental behaviour is hard. There's prior art for this, though: https://web.archive.org/web/20121001002815/http://my.opera.com/securitygroup/blog/2012/07/03/operas-cross-network-protection https://web.archive.org/web/20121001002815/http://my.opera.c...
- EE84M3i 6y ago"One website can use resources from other website using img, script, link tags." Interestingly, you can't do this for web fonts, because they require CORS, which was only added to make type foundries happier by making hotlinking fonts not possible.
- deleted 6y ago[deleted]
- cookiengineer 6y agoThis reminds me of the DDoS service that was using adverts on various ad networks to abuse firefox’s ftp:// url support in exactly the same manner, because ftp protocol didn’t have any limitations, so there were 65k connections spawned simultaneously per client/bot.