low
3.6
CWE
NVD-CWE-Other
Advisory Published
Updated

CVE-2006-4226

First published: Fri Aug 18 2006(Updated: )

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.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
MySQL=4.1.0
MySQL=4.1.2
MySQL=4.1.3
MySQL=4.1.8
MySQL=4.1.10
MySQL=4.1.12
MySQL=4.1.13
MySQL=4.1.14
MySQL=4.1.15
MySQL=5.0.0
MySQL=5.0.1
MySQL=5.0.2
MySQL=5.0.3
MySQL=5.0.4
MySQL=5.0.5
MySQL=5.0.5.0.21
MySQL=5.0.10
MySQL=5.0.15
MySQL=5.0.16
MySQL=5.0.17
MySQL=5.0.20
MySQL=5.0.22.1.0.1
MySQL=5.1.5
MySQL=4.0.0
MySQL=4.0.1
MySQL=4.0.2
MySQL=4.0.3
MySQL=4.0.4
MySQL=4.0.5
MySQL=4.0.5a
MySQL=4.0.6
MySQL=4.0.7
MySQL=4.0.7-gamma
MySQL=4.0.8
MySQL=4.0.8-gamma
MySQL=4.0.9
MySQL=4.0.9-gamma
MySQL=4.0.10
MySQL=4.0.11
MySQL=4.0.11-gamma
MySQL=4.0.12
MySQL=4.0.13
MySQL=4.0.14
MySQL=4.0.15
MySQL=4.0.16
MySQL=4.0.17
MySQL=4.0.18
MySQL=4.0.19
MySQL=4.0.20
MySQL=4.0.21
MySQL=4.0.23
MySQL=4.0.24
MySQL=4.0.25
MySQL=4.0.26
MySQL=4.0.27
MySQL=4.1.0-alpha
MySQL=4.1.1
MySQL=4.1.2-alpha
MySQL=4.1.3-beta
MySQL=4.1.4
MySQL=4.1.5
MySQL=4.1.6
MySQL=4.1.7
MySQL=4.1.9
MySQL=4.1.11
MySQL=4.1.16
MySQL=4.1.17
MySQL=4.1.18
MySQL=4.1.19
MySQL=4.1.20
MySQL=4.1.21
MySQL=5.0.0-alpha
MySQL=5.0.3-beta
MySQL=5.0.6
MySQL=5.0.7
MySQL=5.0.8
MySQL=5.0.9
MySQL=5.0.11
MySQL=5.0.12
MySQL=5.0.13
MySQL=5.0.14
MySQL=5.0.18
MySQL=5.0.19
MySQL=5.0.21
MySQL=5.0.22
MySQL=5.1.1
MySQL=5.1.2
MySQL=5.1.3
MySQL=5.1.4
MySQL=5.1.6
MySQL=5.1.7
MySQL=5.1.8
MySQL=5.1.9
MySQL=5.1.10
MySQL=5.1.11

Remedy

http://bugs.mysql.com/bug.php?id=17647

Remedy

http://dev.mysql.com/doc/refman/5.0/en/news-5-0-25.html

Remedy

http://lists.mysql.com/commits/5927

Remedy

http://secunia.com/advisories/21506

Remedy

http://www.securityfocus.com/bid/19559

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

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.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203