2 ms·
You could do a load of damage with DNS redirection. If you look at the market penetration of Google Analytics you'll see that a very, very large number of site
by jgrahamc 17y ago
You could do a load of damage with DNS redirection. If you look at the market penetration of Google Analytics you'll see that a very, very large number of sites are embedding JavaScript pulled from google-analytics.com in web pages. Now imagine if you redirected that one domain and served your own JavaScript. You could include the GA JavaScript as well, but add your own stuff which would then run in everyone's (within that DNS area) web pages and your JavaScript could start doing all sorts of nasty things.
- jacquesm 17y agoAbsolutely, I don't think it will be long before there will be a major hack like this at some large ISP. The temptation is just too large. DNS is one of the weak links of the way the web is put together, and javascript embedded from third party sites nicely exposes that Achilles heel. Another reason to mistrust open wifi connections :)
- froo 17y agoYou wouldn't even need to do too much damage on the client side for an effective attack vector. Imagine redirecting scripts for googleadservices.com and implementing their JS code with your own publisher ID there. That would make some of those adsense cheques Markus Frind has shown off look like lunch money. EDIT - if you really wanted to make something like this cool, you would instead use the publisher ID of some random charity (or even cycle through an array of charities) that could be easily obtainable by viewing source code in pages. Just a thought... EDIT #2 - Or, some more Internet Justice - just have it ignore the clicks that would otherwise go to domain parkers (with the revenue heading to charity). You cut off that air supply and eventually a lot of domains will start becoming available again. That way, the Internet Wins.