Simple Backdoor on WordPress
The Wordpress development team has posted an announcement that the download server had been hacked, and wordpress 2.1.1 had a backdoor included in it allowing for remote code execution.URL: http://wordpress.org/development/2007/03/upgrade-212/
[update: the exploit code is here: http://www.securityfocus.com/archive/1/461794/30/0/threaded (how come I am still one of the few that think that we need Sandboxes?)]
nice, the business model is evolving.
But this is still a very ‘inefficient’ attack since:
a) the final binaries were the ones infected (very easy to detect (imagine if the infected code was actually from ‘real’ SVN source code and made from a ‘trusted’ developer))
b) by the speed this was detected the exploit (and the blog page didn’t give a lot of details about it) must have been a very ‘HEY I AM A BACKDOOR!!!!’ kind of code. A real exploit would be one that (using a .NET example) used a type confusion attack to insert a buffer overflow on a remotely accessible method (which would be inserted in day X and only used a couple months later).
but it’s evolving…..
Can everybody that writes code and has a Browser window open under the same user account (even if non admin) raise their hand? … nice so many hands (including mine)…. guess what, if your browser is 0wned, so will be your code..
And OWASP uses WordPress (although Mike tells me that we were not affected) for our blogs (blogs.owasp.org), nice 
I am still waiting for the day that we will be maliciously hacked for commercial reasons since that will be another step in the evolution of the malicious guy’s business model
Dinis in San Jose