CVE-2010-3836: Medium severity mysql vulnerability
A flaw in MySQL versions prior to 5.1.51 [1] was reported [2] that could allow an authenticated user to kill connections to MySQL. Upstream describes the problem as follows:
IN quantified predicates are never executed directly. They are rather wrapped inside nodes called IN Optimizers (Iteminoptimizer) which take care of the execution. However, this is not done during view preparation. Unfortunately the LIKE predicate pre-evaluates constant right-hand side arguments even during name resolution within view preparation. Likely this is meant as an optimization.
There is a patch for this available [3].
[1] http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html [2] http://bugs.mysql.com/bug.php?id=54568 [3] http://lists.mysql.com/commits/112602
Other sources
MySQL 5.0 before 5.0.92, 5.1 before 5.1.51, and 5.5 before 5.5.6 allows remote authenticated users to cause a denial of service (assertion failure and server crash) via vectors related to view preparation, pre-evaluation of LIKE predicates, and IN Optimizers.
— MITRE
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2010-3836?
CVE-2010-3836 has been designated as a moderate severity vulnerability in MySQL.
How do I fix CVE-2010-3836?
To fix CVE-2010-3836, you should upgrade to MySQL version 5.1.51 or later.
What does CVE-2010-3836 allow an authenticated user to do?
CVE-2010-3836 allows an authenticated user to kill connections to MySQL.
Which versions of MySQL are affected by CVE-2010-3836?
CVE-2010-3836 affects MySQL versions prior to 5.1.51.
Is there a workaround for CVE-2010-3836?
There is no official workaround for CVE-2010-3836; upgrading is recommended.