MySQL.com hacked via... SQL injection vuln
*facepalm*
Regcast training : Hyper-V 3.0, VM high availability and disaster recovery
MySQL.com was hacked over the weekend via an attack which used a blind SQL injection exploit to pull off the pawnage.
Hackers extracted usernames and password hashes from the site, which were subsequently posted to pastebin.com. Any easy to guess login credentials could be easily extracted from this data using rainbow tables to match dictionary passwords to their hash values.
This information revealed that the director of product management for WordPress at MySQL1 used a four digit number as his password, among other snippets, net security firm Sophos reports.
Romanian grey-hat hackers TinKode and Ne0h of Slacker.Ro claimed responsibility for the attack.
MySQL offers open source-based database software and services to enterprises.
Security practices at MySQL.com obviously left quite a lot to be desired. As well as the vulnerability actually used to pull off the attack MySQL.com has been vulnerable to XSS exploits since January, according to XSSed.com.
MySQL's parent company Sun/Oracle was also hit by the same hackers, who extracted emails from compromised websites. Login credentials were not compromised in that case. ®
1 This chap works for MySQL not Wordpress, as incorrectly stated in the first version of this article.
COMMENTS
Two or three steps above EPIC fail
oh, and the https certificate for the customer.mysql.com domain expired a month ago
You have totally missed the point
Using a salt renders any 'rainbow tables' completely useless, therefore it is not trivial to automatically extract plaintext passowrds from their hashes in the database.
Also, if the designers of the system have a brain, the salt value will be stored in a file and not in the database itself. To get the salt value would likely require a totally different entry point for the hack. It would most certainly NOT be exposed by a database injection exploit.
Even if the salt value itself is compromised, a new rainbow table would have to be created specially for that particular salt value. While not impossible, it is significantly more hassle and more computationally expensive than using a pre-compiled rainbow table.
Oh, and it is worth noting that Grendel did not actually reveal what his salt value is.
IT infrastructure monitoring strategies
Agentless Backup is Not a Myth
Top 10 SIEM implementer’s checklist
Steps to Take Before Choosing a Business Continuity Partner
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider
