Vulnerabilities · 2005 · Mysql
CVE-2005-1636
Mysql vulnerability
mysql_install_db in MySQL 4.1.x before 4.1.12 and 5.x up to 5.0.4 creates the mysql_install_db.X file with a predictable filename and insecure permissions, which allows local users to execute arbitrary SQL commands by modifying the file's contents.
Affected products
Mysql. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Mysql runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- marc.info/?l=full-disclosure&m=111632686805498&w=2
- secunia.com/advisories/15369
- secunia.com/advisories/17080
- www.mandriva.com/security/advisories?name=MDKSA-2006:045
- www.redhat.com/support/errata/RHSA-2005-685.html
- www.securityfocus.com/bid/13660
- www.zataz.net/adviso/mysql-05172005.txt
- bugzilla.redhat.com/bugzilla/show_bug.cgi?id=158688
- nvd.nist.gov/vuln/detail/CVE-2005-1636
- cve.org/CVERecord?id=CVE-2005-1636
More vulnerabilities in Mysql products
CVE-2017-15945CVE-2015-2575CVE-2013-1492CVE-2012-2749CVE-2012-2102CVE-2012-1696CVE-2012-0882CVE-2012-0583All 110
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.