Just a heads up about a post I read on Webhostingtalk: "CVE-2012-2122 :: Security vulnerability in MySQL/MariaDB (possibly percona)": http://www.webhostingtalk.com/showthread.php?p=8177080
Direct link: http://seclists.org/oss-sec/2012/q2/493
However MySQL versions from 5.1.63 and 5.5.24 are not affected. Custombuild has newest MySQL 5.1.63 and MySQL 5.5.25, so if you have upgraded to newest MySQL 5.1.x or 5.5.x, you should be safe - if not I would suggest upgrading now!
Quote from http://seclists.org/oss-sec/2012/q2/493
Edit: It seems MySQL 5.0.x might be vunlerable and without any fix (because it is not supported any longer), so if you still run MySQL 5.0.x, it is time to upgrade!
Direct link: http://seclists.org/oss-sec/2012/q2/493
However MySQL versions from 5.1.63 and 5.5.24 are not affected. Custombuild has newest MySQL 5.1.63 and MySQL 5.5.25, so if you have upgraded to newest MySQL 5.1.x or 5.5.x, you should be safe - if not I would suggest upgrading now!
Quote from http://seclists.org/oss-sec/2012/q2/493
Which means, if one knows a user name to connect (and "root" almost
always exists), she can connect using *any* password by repeating
connection attempts. ~300 attempts takes only a fraction of second, so
basically account password protection is as good as nonexistent.
Any client will do, there's no need for a special libmysqlclient library.
Edit: It seems MySQL 5.0.x might be vunlerable and without any fix (because it is not supported any longer), so if you still run MySQL 5.0.x, it is time to upgrade!
Last edited: