CWE
134
Advisory Published
Updated

CVE-2008-3963

First published: Wed Sep 10 2008(Updated: )

MySQL 5.0 before 5.0.66, 5.1 before 5.1.26, and 6.0 before 6.0.6 does not properly handle a b'' (b single-quote single-quote) token, aka an empty bit-string literal, which allows remote attackers to cause a denial of service (daemon crash) by using this token in a SQL statement.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
MySQL (MySQL-common)=5.0.5
MySQL (MySQL-common)=5.0.10
MySQL (MySQL-common)=5.0.54
MySQL (MySQL-common)=5.0.0
MySQL (MySQL-common)=5.1.23
MySQL (MySQL-common)=5.0.15
MySQL (MySQL-common)=5.0.17
MySQL (MySQL-common)=5.0.5.0.21
MySQL (MySQL-common)=5.0.3
MySQL (MySQL-common)=5.0.44
MySQL (MySQL-common)=5.0.56
MySQL (MySQL-common)=5.0.60
MySQL (MySQL-common)=5.0.24
MySQL (MySQL-common)=5.0.2
MySQL (MySQL-common)=5.0.22.1.0.1
MySQL (MySQL-common)=5.0.30
MySQL (MySQL-common)=5.0.20
MySQL (MySQL-common)=5.0.1
MySQL (MySQL-common)=5.0.4
MySQL (MySQL-common)=5.0.36
MySQL (MySQL-common)=5.0.16
MySQL (MySQL-common)=5.1.5
Oracle MySQL=6.0.0
Oracle MySQL=6.0.1
Oracle MySQL=6.0.2
Oracle MySQL=6.0.3
Oracle MySQL=6.0.4
Oracle MySQL=5.0.50
Oracle MySQL=5.0.51
Oracle MySQL=5.0.0-alpha
Oracle MySQL=5.0.6
Oracle MySQL=5.0.23
Oracle MySQL=5.0.25
Oracle MySQL=5.0.26
Oracle MySQL=5.0.30-sp1
Oracle MySQL=5.0.32
Oracle MySQL=5.0.33
Oracle MySQL=5.0.38
Oracle MySQL=5.0.41
Oracle MySQL=5.0.42
Oracle MySQL=5.0.45
Oracle MySQL=5.0.52
Oracle MySQL=5.1
Oracle MySQL=5.1.1
Oracle MySQL=5.1.2
Oracle MySQL=5.1.3
Oracle MySQL=5.1.4
Oracle MySQL=5.1.6
Oracle MySQL=5.1.7
Oracle MySQL=5.1.8
Oracle MySQL=5.1.9
Oracle MySQL=5.1.10
Oracle MySQL=5.1.11
Oracle MySQL=5.1.12
Oracle MySQL=5.1.13
Oracle MySQL=5.1.14
Oracle MySQL=5.1.15
Oracle MySQL=5.1.16
Oracle MySQL=5.1.17
Oracle MySQL=5.1.18
Oracle MySQL=5.1.19
Oracle MySQL=5.1.20
Oracle MySQL=5.1.21
Oracle MySQL=5.1.22

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.

Frequently Asked Questions

  • What is the severity of CVE-2008-3963?

    CVE-2008-3963 has a severity rating that can lead to a denial of service due to a daemon crash.

  • How do I fix CVE-2008-3963?

    To fix CVE-2008-3963, upgrade MySQL to version 5.0.66 or later, or 5.1.26 or later.

  • Which versions of MySQL are affected by CVE-2008-3963?

    CVE-2008-3963 affects MySQL versions prior to 5.0.66, 5.1.26, and 6.0.6.

  • Can CVE-2008-3963 be exploited remotely?

    Yes, CVE-2008-3963 can be exploited remotely by sending a specially crafted SQL statement.

  • What type of attack does CVE-2008-3963 enable?

    CVE-2008-3963 enables a denial of service attack, resulting in a crash of the MySQL daemon.

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