Strix
26.1K

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

EPSS Probability
6.46%

92.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
MysqlMysql5.0.0—
MysqlMysql5.0.1—
MysqlMysql5.0.2—
MysqlMysql5.0.3—
MysqlMysql5.0.4—
MysqlMysql5.0.5—
MysqlMysql5.0.5.0.21—
MysqlMysql5.0.10—
MysqlMysql5.0.15—
MysqlMysql5.0.16—
MysqlMysql5.0.17—
MysqlMysql5.0.20—
MysqlMysql5.0.22.1.0.1—
MysqlMysql5.0.24—
MysqlMysql5.0.30—
MysqlMysql5.0.36—
MysqlMysql5.0.44—
MysqlMysql5.0.54—
MysqlMysql5.0.56—
MysqlMysql5.0.60—
MysqlMysql5.1.5—
MysqlMysql5.1.23—
OracleMysql5.0.0Alpha
OracleMysql5.0.6—
OracleMysql5.0.23—
OracleMysql5.0.25—
OracleMysql5.0.26—
OracleMysql5.0.30Sp1
OracleMysql5.0.32—
OracleMysql5.0.33—
OracleMysql5.0.38—
OracleMysql5.0.41—
OracleMysql5.0.42—
OracleMysql5.0.45—
OracleMysql5.0.50—
OracleMysql5.0.51—
OracleMysql5.0.52—
OracleMysql5.1—
OracleMysql5.1.1—
OracleMysql5.1.2—
OracleMysql5.1.3—
OracleMysql5.1.4—
OracleMysql5.1.6—
OracleMysql5.1.7—
OracleMysql5.1.8—
OracleMysql5.1.9—
OracleMysql5.1.10—
OracleMysql5.1.11—
OracleMysql5.1.12—
OracleMysql5.1.13—

Showing 50 of 64 affected configurations. See NVD for the full list.

References

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.

Are you affected by CVE-2008-3963?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST