CVE-2010-3680: Medium severity MySQL mysql vulnerability
A denial of service was found in the way MySQL processed creation of temporary tables, when the InnoDB storage engine was used. A remote authenticated MySQL user could use this flaw to cause mysqld daemon abort (assertion failure).
References: [1] http://secunia.com/advisories/41048/ [2] http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html
Upstream bug report: [3] http://bugs.mysql.com/bug.php?id=54044
Note: This issue only causes a temporary denial of service, as the mysql daemon shipped with Red Hat Enterprise Linux 5 will be automatically restarted after the abort.
Other sources
Oracle MySQL 5.1 before 5.1.49 allows remote authenticated users to cause a denial of service (mysqld daemon crash) by creating temporary tables with nullable columns while using InnoDB, which triggers an assertion failure.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2010-3680?
CVE-2010-3680 is categorized as a denial of service vulnerability that can cause the MySQL server to abort.
How do I fix CVE-2010-3680?
To fix CVE-2010-3680, upgrade MySQL to a version that is not affected by this vulnerability, such as 5.1.49 or later.
What is the impact of CVE-2010-3680 on MySQL systems?
CVE-2010-3680 can lead to a complete denial of service by causing the mysqld daemon to crash when creating temporary tables.
Which versions of MySQL are affected by CVE-2010-3680?
CVE-2010-3680 affects various versions of MySQL 5.1, including 5.1.5 up to 5.1.48.
Who can exploit CVE-2010-3680?
CVE-2010-3680 can be exploited by remote authenticated MySQL users who can create temporary tables.