Proving that no website is ever truly secure, it is being reported that MySQL.com has succumbed to a SQL injection attack. It was first disclosed to the Full Disclosure mailing list early this morning. Hackers have now posted a dump of usernames and password hashes to pastebin.com.
Most embarrassingly, the Director of Product Management's WordPress password was set to a four digit number... his ATM PIN perhaps? Several accounts had passwords like "qa". The irony is that they weren't compromised by means of their ridiculously simple passwords, but rather flaws in the implementation of their site.
MySQL's parent company Sun/Oracle has also been attacked. Both tables and emails were dumped from their databases, but no passwords.
It does not appear to be a vulnerability in the MySQL software, but rather flaws in the implementation of their websites.
Auditing your websites for SQL injection is an essential practice, as well as using secure passwords.
Either can lead you down a road that ends in tears. If you haven't reviewed your web coding practices, this might be a good time to perform an audit of your public-facing assets to be sure your organization won't become the next headline.
It was noted on Twitter that mysql.com is also subject to an XSS (cross-site scripting) vulnerability that was reported in January 2011 and has not been remedied.
![Password security infomerical leaves Ellen DeGeneres in disbelief.. and it will you too [VIDEO]](http://sophosnews.files.wordpress.com/2013/04/ellen-thumb.jpg?w=75&h=75&crop=1)
![Can multiple moving cursors really hide your password from spyware and peepers? [VIDEO]](http://sophosnews.files.wordpress.com/2013/03/cursors-thumb.jpg?w=75&h=75&crop=1)
![Hacked TV channels broadcast zombie apocalypse emergency alert [VIDEO]](http://sophosnews.files.wordpress.com/2013/02/zombie-thumb.jpg?w=75&h=75&crop=1)
Well...that's great! MySQL not secure means we wait for some hacker interested in our site to waltz in? MySQL.com--fix the holes. Please.
JDMan: 4th paragraph from the bottom clearly states "It does not appear to be a vulnerability in the MySQL software, but rather flaws in the implementation of their websites.".
SQL injection is about not sanitizing input data, it has nothing to do with "holes" in the MySQL software itself.
How embarrassing...
MySQL's flaws are its two-layer architecture; this is what causes the SQL injection and its vulnerabilities.
MySQL is fast, granted. However, if this continues I'll be moving to something more secure.
Little Bobby Tables strikes again-
http://xkcd.com/327/
There are still web developers out there who don't understand SQL injection? Scripting injection attacks were covered in the beginner's programming classes I remember twenty years ago. You don't need SQL or the Web to understand the theory of input validation in software. Only an unskilled developer would make such a rookie mistake.
I have seen companies with a lot of money to spare hire only the smallest teams of the least skilled developers for their websites because they are cheap to a fault and have no appreciation for the actual skill involved.
The one time in my life I ran into SQL injection troubles was when I used an off-the-shelf component that contained them. Definitely something to consider when you start using third party software.
As http://xssed.com/search?key=mysql says, a bunch of old bugs seems to be getting fixed.
The old ones embarassed me much more than the new hack ...
So my question is, was it the open source guys or the Oracle guys who had the crappy passwords?
=;^)