Javascript Spider
During the last couple of days I have been testing several attack vectors to circumvent the browser security sandbox also known as "the same origin policy". There is a lot involved into this subject and I will present my notes very soon.
The JavaScript Spider is the first implementation of a proof of concept tool which shows that Javascript can be in fact quite malicious. This implementation depends on proxydrop.com but other proxies can be used too: Google Translate is one of them. Keep in mind that the tool spiders only one page.
As you can see, publicly available anonymizing proxies can be used to fetch remote pages. This technique will work quite successfully on Internet resources but not on Intranet. The reason for this is obvious.
The requests made are anonymous since they are proxied. This may amplify or reduce the risk depending on the situation. However an anonymous self-propagating worm can be in theory - possible.
Archived Comments
carrier of an infectious agent; capable of transmitting infection from one host to another; especially the animal that transfers an infectious agent from one host to another, usually an arthropod. life.umd.edu
A vector is a number (a magnitude) together with a direction (compare with scalar). A vector can be represented by an arrow whose length represents the magnitude and the direction represents the direction. enchantedlearning.comIt is more than obvious what attack vector is. You are also saying:
Honestly, the only thing that you 'discovered' (and that was just something you noticed, as the world has passed you by) is that publicly-accessible anonymous proxies can be used for "bad" things.You are right for one thing. Publicly accessible proxies can be used for bad things and that's nothing new. However, who has done it in the past with JavaScript? I couldn't find anything like this on the web and to me it is a new thing. John, I am very interested to see your opinion on this respond. Many thanks.
Using a publicly-accessible anonymous proxy is hardly a security concern - especially considering that none of the user's personal information is passed along.John, you apparently didn't understand the post at all. He's not claiming that those using proxies are at greater risk, or that their personal information can be disclosed by it. It has nothing to do with proxy users. It's saying that by using certain public proxies you can work around the javascript's same origin policies. If you bothered reading his previous blog posts about Google Search API Worms, you'd understand. Another tool in the arsenal, alongside google and yahoo's APIs This may help you comprehend the security restrictions of javascript: http://www.windowsitlibrary.com/Content/1160/22/1.html -maluc