Twitter Suffers Web Interface Exploit
HaloZero writes "We're seeing lots of re-tweets on Twitter.com right now, all containing a fragment of JavaScript, which re-tweets itself when moused-over on the Twitter web interface. This could easily be muted into a more sinister attack, so it is recommended that you use a third party client application, or refrain from social media altogether until the problem is resolved."
http://t.co/@"onmouseover="document.getElementById('status').value='RT test_nau';$('.status-update-form').submit();"style="background:red"/
Before you mod me down, please consider the fact that I have a sense of humour plus I posted using "Plain Old Text" plus the script does not work on Slashdot.
If you want to use the web interface, the mobile version isn't affected: http://m.twitter.com/
catch (HumourFailureException e) { e.user.send("You, sir, are a humourless idiot."); }
Why, again, should I be using Twitter?
Trolling is a art,
You'd think people would've learned by now that you can't allow random strings of script in user-submitted data. Why is filtering this stuff out not part of standard input sanitization practices by now?
Add "t.co" to your Windows Hosts file - this will stop the jibberish text.
Although the web interface is still broke. (The interface goes grey, and
any click still tries to go to the t.co web page)
Add this to your Hosts file:
0.0.0.0 t.co
http://xkcd.com/327/
There's more info on the spread of this exploit from Paul Mutton at Netcraft and Graham Cluely at Sophos.
It is now FIXED.
http://twitter.com/delbius/status/25120366027
catch (HumourFailureException e) { e.user.send("You, sir, are a humourless idiot."); }
I'm sorry, but 1994 called, and it wants its World Wide Web back. Interactive webpages are the future, they are actually really nice when they're done properly, and denying that is just holding you back. I expect that sooner or later secure programming mentalities will become deeply ingrained in Web programming, and things like this will stop happening. There will always be bugs, but that's no different from any other software.
NoScript is a much better solution than out-and-out disabling javascript anyways.
"refrain from social media altogether until the problem is resolved"
I've been doing exactly that, and intend on keeping to do that until the problem of Twitter has been resolved.
What a depressingly stupid machine.
1994 called, and it wants its World Wide Web back.
I called, and I want 1994's WWW back. No more "My entire website is in Flash!" No more drive-by downloads. No more web-apps that just write a static page when HTML would have sufficed. <blink>Just "Here's my Dog!" and "Work in Progress" signs.</blink>