First published: Tue May 17 2005(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
MySQL (MySQL-common) | =5.0.1 | |
MySQL (MySQL-common) | =5.0.2 | |
MySQL (MySQL-common) | =5.0.3 | |
MySQL (MySQL-common) | =5.0.4 | |
Oracle MySQL | =4.0.0 | |
Oracle MySQL | =4.0.1 | |
Oracle MySQL | =4.0.2 | |
Oracle MySQL | =4.0.3 | |
Oracle MySQL | =4.0.4 | |
Oracle MySQL | =4.0.5 | |
Oracle MySQL | =4.0.5a | |
Oracle MySQL | =4.0.6 | |
Oracle MySQL | =4.0.7 | |
Oracle MySQL | =4.0.7-gamma | |
Oracle MySQL | =4.0.8 | |
Oracle MySQL | =4.0.8-gamma | |
Oracle MySQL | =4.0.9 | |
Oracle MySQL | =4.0.9-gamma | |
Oracle MySQL | =4.0.10 | |
Oracle MySQL | =4.0.11 | |
Oracle MySQL | =4.0.11-gamma | |
Oracle MySQL | =5.0.0-alpha |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2005-1636 is considered a medium severity vulnerability due to the potential for local users to exploit it to execute arbitrary SQL commands.
To fix CVE-2005-1636, upgrade to latest versions of MySQL that are not affected, specifically versions 4.1.12 or higher and 5.0.5 or higher.
The impact of CVE-2005-1636 allows local users to modify the mysql_install_db.X file and execute unauthorized SQL commands.
CVE-2005-1636 affects MySQL versions 4.1.x before 4.1.12 and 5.x up to 5.0.4.
CVE-2005-1636 cannot be exploited remotely as it requires local user access to exploit the vulnerability.