-
Website
http://mashable.com/ -
Original page
http://mashable.com/2007/06/01/spyjax/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Robert Basil
142 comments · 8 points
-
Jennifer Van Grove
149 comments · 23 points
-
r0cketman22
317 comments · 52 points
-
rajagiri4
160 comments · 2 points
-
barringtonarch
150 comments · 4 points
-
-
Popular Threads
-
Enter the Zappos Sharing Happiness $3,000 Shopping Spree Giveaway Contest
11 hours ago · 111 comments
-
REVEALED: Details on YouTube’s VEVO Music Video Site
3 hours ago · 12 comments
-
Redbox: The Enemy of the Entertainment Industry? [STUDY]
3 hours ago · 9 comments
-
Holiday Mojo: What Kind of Seasonal Twitter User Are You?
4 hours ago · 14 comments
-
Head to Head: Chrome for Mac vs. Chrome for Windows
7 hours ago · 22 comments
-
Enter the Zappos Sharing Happiness $3,000 Shopping Spree Giveaway Contest
Could that trick Spyjax?
Very evil either way.
My suggestion is to run the Stanford Anti-Phishing SafeHistory Firefox and LocalRodeo extensions.
http://safehistory.com/
http://crypto.stanford.edu/sameorigin/
Some of the links return 404's but there is still good content about other types of querying. There is also a link to a related Firefox extensions called SafeCache.
There's a 3-4 year old bug filed in the Mozilla code base for this .... it can't be fixed because fixing it would break the fundamental way the web works.
Sorry :)
For all intents and purposes the amount of possible colours is limitless, plus it would probably more processor-intensive to check that.
Kevin Burton, I believe that this was filed already, but how could changing something in Mozilla software change the way the WWW works?
If I write a piece of software that tries to interact with the WWW somehow, it won't change anything about it.
Anyway, it sounds to me this is a security issue with JavaScript and nothing else.
Someone would need to remove support for checking link status (or whatever the proper name is) in there to really remove the vulnerability.