CVE-2008-3963
UnknownEPSS 6.46%
Last modified
CVE-2008-3963 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 6.46% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Mysql | Mysql | 5.0.0 | — |
| Mysql | Mysql | 5.0.1 | — |
| Mysql | Mysql | 5.0.2 | — |
| Mysql | Mysql | 5.0.3 | — |
| Mysql | Mysql | 5.0.4 | — |
| Mysql | Mysql | 5.0.5 | — |
| Mysql | Mysql | 5.0.5.0.21 | — |
| Mysql | Mysql | 5.0.10 | — |
| Mysql | Mysql | 5.0.15 | — |
| Mysql | Mysql | 5.0.16 | — |
| Mysql | Mysql | 5.0.17 | — |
| Mysql | Mysql | 5.0.20 | — |
| Mysql | Mysql | 5.0.22.1.0.1 | — |
| Mysql | Mysql | 5.0.24 | — |
| Mysql | Mysql | 5.0.30 | — |
| Mysql | Mysql | 5.0.36 | — |
| Mysql | Mysql | 5.0.44 | — |
| Mysql | Mysql | 5.0.54 | — |
| Mysql | Mysql | 5.0.56 | — |
| Mysql | Mysql | 5.0.60 | — |
| Mysql | Mysql | 5.1.5 | — |
| Mysql | Mysql | 5.1.23 | — |
| 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.50 | — |
| Oracle | Mysql | 5.0.51 | — |
| 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 | — |
Showing 50 of 64 affected configurations. See NVD for the full list.
References
- http://secunia.com/advisories/31769Vendor Advisory
- http://secunia.com/advisories/32759Vendor Advisory
- http://secunia.com/advisories/34907Vendor Advisory
- http://www.vupen.com/english/advisories/2008/2554Vendor Advisory
- http://secunia.com/advisories/31769Vendor Advisory
- http://secunia.com/advisories/32759Vendor Advisory
- http://secunia.com/advisories/34907Vendor Advisory
- http://www.vupen.com/english/advisories/2008/2554Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2008-3963?
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.
How severe is CVE-2008-3963?
Severity scoring for CVE-2008-3963 is pending analysis. The EPSS model estimates a 6.46% probability of exploitation in the next 30 days.
How do I fix CVE-2008-3963?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2008
- CVE-2008-3957The Microsoft Windows Image Acquisition Logger ActiveX contr…
- CVE-2008-3958IBM DB2 UDB 8 before Fixpak 17 allows remote attackers to ca…
- CVE-2008-3959IBM DB2 UDB 8.1 before FixPak 16, 8.2 before FixPak 9, and 9…
- CVE-2008-3960Unspecified vulnerability in the JDBC Applet Server Service …
- CVE-2008-3961Multiple unspecified vulnerabilities in Adobe Illustrator CS…
- CVE-2008-3962The from_format function in ssmtp.c in ssmtp 2.61 and 2.62, …
- CVE-2008-3964Multiple off-by-one errors in libpng before 1.2.32beta01, an…
- CVE-2008-3965SQL injection vulnerability in misc.php in MyBB (aka MyBulle…
- CVE-2008-3966Multiple cross-site scripting (XSS) vulnerabilities in MyBB …
- CVE-2008-3967moderation.php in MyBB (aka MyBulletinBoard) before 1.4.1 do…
- CVE-2008-3968Cross-site scripting (XSS) vulnerability in userlist.php in …
- CVE-2008-3969Multiple unspecified vulnerabilities in BitlBee before 1.2.3…
Are you affected by CVE-2008-3963?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST