CVE-2006-4226: Low severity MySQL mysql vulnerability
MySQL before 4.1.21, 5.0 before 5.0.25, and 5.1 before 5.1.12, when run on case-sensitive filesystems, allows remote authenticated users to create or access a database when the database name differs only in case from a database for which they have permissions.
Affected Software
Remediation
Patch Available
Patch Available
Patch Available
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2006-4226?
CVE-2006-4226 has a moderate severity rating due to the potential for unauthorized access to databases via case-sensitive filesystem exploitation.
How do I fix CVE-2006-4226?
To fix CVE-2006-4226, upgrade MySQL to version 4.1.21, 5.0.25, or 5.1.12 or later.
Who is affected by CVE-2006-4226?
CVE-2006-4226 affects remote authenticated users of MySQL versions prior to 4.1.21, 5.0.25, and 5.1.12 running on case-sensitive filesystems.
What is the impact of CVE-2006-4226?
The impact of CVE-2006-4226 allows authenticated users to create or access databases with names that differ only in case from existing databases.
Is there a workaround for CVE-2006-4226?
A workaround for CVE-2006-4226 is to configure MySQL to run on a case-insensitive filesystem.