First published: Wed Oct 06 2010(Updated: )
A flaw in MySQL versions prior to 5.1.51 [1] was reported [2] that could allow an authenticated user to cause the MySQL server to enter an infinite loop by creating a query with nested JOINs when used from stored procedures and prepared statements. [1] <a href="http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html">http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html</a> [2] <a href="http://bugs.mysql.com/bug.php?id=53544">http://bugs.mysql.com/bug.php?id=53544</a> This affects MySQL 5.x, but MySQL 4.x and early do not have support for stored procedures. This causes CPU consumption around 95-100%, however connections and queries to the database can continue. Killing the query itself is ineffective, and even a 'service mysqld restart' will fail unless the mysqld process that is handling the query is forcibly killed.
Affected Software | Affected Version | How to fix |
---|---|---|
MySQL (MySQL-common) | <5.1.51 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
MySQL versions prior to 5.1.51 are affected by REDHAT-BUG-640861.
REDHAT-BUG-640861 identifies a flaw that can cause the MySQL server to enter an infinite loop.
An authenticated user can create a query with nested JOINs in stored procedures and prepared statements to trigger the issue.
To address REDHAT-BUG-640861, you should upgrade to MySQL version 5.1.51 or later.
Exploiting REDHAT-BUG-640861 can lead to service disruptions due to the server entering an infinite loop.