low
2.1
CWE
NVD-CWE-Other
Advisory Published
Updated

CVE-2006-4031

First published: Wed Aug 09 2006(Updated: )

MySQL 4.1 before 4.1.21 and 5.0 before 5.0.24 allows a local user to access a table through a previously created MERGE table, even after the user's privileges are revoked for the original table, which might violate intended security policy.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
MySQL=5.0.5
MySQL=5.0.10
MySQL=5.0.15
MySQL=5.0.17
MySQL=4.1.13
MySQL=5.0.5.0.21
MySQL=5.0.3
MySQL=4.1.15
MySQL=4.1.8
MySQL=4.1.14
MySQL=4.1.12
MySQL=4.1.10
MySQL=5.0.2
MySQL=5.0.22.1.0.1
MySQL=5.0.20
MySQL=5.0.1
MySQL=4.1.0
MySQL=5.0.4
MySQL=4.1.3
MySQL=5.0.16
MySQL=4.1.2
MySQL=3.22.27
MySQL=3.22.28
MySQL=3.22.29
MySQL=3.22.30
MySQL=3.22.32
MySQL=3.23
MySQL=3.23.0-alpha
MySQL=3.23.1
MySQL=3.23.2
MySQL=3.23.3
MySQL=3.23.4
MySQL=3.23.5
MySQL=3.23.6
MySQL=3.23.7
MySQL=3.23.8
MySQL=3.23.9
MySQL=3.23.10
MySQL=3.23.11
MySQL=3.23.12
MySQL=3.23.13
MySQL=3.23.14
MySQL=3.23.15
MySQL=3.23.16
MySQL=3.23.17
MySQL=3.23.18
MySQL=3.23.19
MySQL=3.23.20-beta
MySQL=3.23.21
MySQL=3.23.22
MySQL=3.23.23
MySQL=3.23.24
MySQL=3.23.25
MySQL=3.23.26
MySQL=3.23.27
MySQL=3.23.28-gamma
MySQL=3.23.28
MySQL=3.23.29
MySQL=3.23.30
MySQL=3.23.31
MySQL=3.23.32
MySQL=3.23.33
MySQL=3.23.34
MySQL=3.23.35
MySQL=3.23.36
MySQL=3.23.37
MySQL=3.23.38
MySQL=3.23.39
MySQL=3.23.40
MySQL=3.23.41
MySQL=3.23.42
MySQL=3.23.43
MySQL=3.23.44
MySQL=3.23.45
MySQL=3.23.46
MySQL=3.23.47
MySQL=3.23.48
MySQL=3.23.49
MySQL=3.23.50
MySQL=3.23.51
MySQL=3.23.52
MySQL=3.23.53
MySQL=3.23.53a
MySQL=3.23.54
MySQL=3.23.54a
MySQL=3.23.55
MySQL=3.23.56
MySQL=3.23.57
MySQL=3.23.58
MySQL=3.23.59
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-gamma
MySQL=4.0.8
MySQL=4.0.9
MySQL=4.0.9-gamma
MySQL=4.0.10
MySQL=4.0.11-gamma
MySQL=4.0.11
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=5.0.0-alpha
MySQL=5.0.3-beta
MySQL=5.0.6
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.0.7
MySQL=5.0.8
MySQL=5.0.9

Remedy

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

Remedy

http://dev.mysql.com/doc/refman/4.1/en/news-4-1-21.html

Remedy

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

Remedy

http://secunia.com/advisories/21259

Remedy

http://securitytracker.com/id?1016617

Remedy

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

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-4031?

    CVE-2006-4031 is classified as a medium severity vulnerability.

  • How do I fix CVE-2006-4031?

    To fix CVE-2006-4031, upgrade to MySQL versions 4.1.21 or later, or 5.0.24 or later.

  • What impact does CVE-2006-4031 have on MySQL security?

    CVE-2006-4031 allows revoked users to access tables via MERGE tables, potentially violating data security policies.

  • Which versions of MySQL are affected by CVE-2006-4031?

    CVE-2006-4031 affects MySQL versions prior to 4.1.21 and 5.0.24.

  • Is CVE-2006-4031 a local or remote vulnerability?

    CVE-2006-4031 is a local vulnerability that requires access to the server.

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