CVE-2010-3838: 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 by creating a query with the GREATEST() or LEAST() functions having a mixed list of numeric and LONGBLOB arguments.
[1] http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html [2] http://bugs.mysql.com/bug.php?id=54461
This is noted as having been fixed in MySQL 5.1.51, but it does not cause a crash on MySQL 5.0.50 in Fedora 13. It also causes a crash on Red Hat Enterprise Linux 5 (5.0.77) but not Red Hat Enterprise Linux 4 (4.1.22).
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 (server crash) via a query that uses the (1) GREATEST or (2) LEAST function with a mixed list of numeric and LONGBLOB arguments, which is not properly handled when the function's result is "processed using an intermediate temporary table."
— MITRE
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2010-3838?
CVE-2010-3838 is classified as a medium severity vulnerability that can lead to denial of service under certain circumstances.
How do I fix CVE-2010-3838?
To mitigate CVE-2010-3838, upgrade your MySQL version to 5.1.51 or later.
What are the affected MySQL versions for CVE-2010-3838?
CVE-2010-3838 affects MySQL versions prior to 5.1.51, including versions 5.1.5 to 5.1.50.
What type of vulnerability is CVE-2010-3838?
CVE-2010-3838 is a denial-of-service vulnerability that allows authenticated users to kill MySQL connections.
Who can exploit CVE-2010-3838?
CVE-2010-3838 can be exploited by any authenticated user who can issue queries to the affected MySQL server.