CVE-2005-1636: Medium severity MySQL mysql vulnerability

Published May 17, 2005

Updated

mysqlinstalldb in MySQL 4.1.x before 4.1.12 and 5.x up to 5.0.4 creates the mysqlinstalldb.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 Software

22 affected components

MySQL mysql=5.0.1

MySQL mysql=5.0.2

MySQL mysql=5.0.3

MySQL mysql=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

Event History

May 17, 2005

CVE Published

04:00 AM

CVE Published

via MITRE·08:00 AM

Data Sourced

via MITRE·08:00 AM

Description

Frequently Asked Questions

What is the severity of CVE-2005-1636?

CVE-2005-1636 is considered a medium severity vulnerability due to the potential for local users to exploit it to execute arbitrary SQL commands.

How do I fix CVE-2005-1636?

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.

What is the impact of CVE-2005-1636?

The impact of CVE-2005-1636 allows local users to modify the mysql_install_db.X file and execute unauthorized SQL commands.

Which MySQL versions are affected by CVE-2005-1636?

CVE-2005-1636 affects MySQL versions 4.1.x before 4.1.12 and 5.x up to 5.0.4.

Can CVE-2005-1636 be exploited remotely?

CVE-2005-1636 cannot be exploited remotely as it requires local user access to exploit the vulnerability.