MySQL did not require privileges such as "SELECT" for the source table in a"CREATE TABLE LIKE" statement. An authenticated user could obtain sensitiveinformation, such as the table structure. (CVE-2007-3781)

A flaw was discovered in MySQL that allowed an authenticated user to gainupdate privileges for a table in another database, via a view that refersto the external table. (CVE-2007-3782)

MySQL did not require the "DROP" privilege for "RENAME TABLE" statements.An authenticated user could use this flaw to rename arbitrary tables.(CVE-2007-2691)

A flaw was discovered in the mysql_change_db function when returning fromSQL SECURITY INVOKER stored routines. An authenticated user could use thisflaw to gain database privileges. (CVE-2007-2692)

MySQL allowed an authenticated user to access a table through a previouslycreated MERGE table, even after the user's privileges were revoked fromthe original table, which might violate intended security policy. This isaddressed by allowing the MERGE storage engine to be disabled, which canbe done by running mysqld with the "--skip-merge" option. (CVE-2006-4031)

MySQL evaluated arguments in the wrong security context, which allowed anauthenticated user to gain privileges through a routine that had been madeavailable using "GRANT EXECUTE". (CVE-2006-4227)

Multiple flaws in MySQL allowed an authenticated user to cause the MySQLdaemon to crash via crafted SQL queries. This only caused a temporarydenial of service, as the MySQL daemon is automatically restarted after thecrash. (CVE-2006-7232, CVE-2007-1420, CVE-2007-2583)

As well, these updated packages fix the following bugs:

* a separate counter was used for "insert delayed" statements, which causedrows to be discarded. In these updated packages, "insert delayed"statements no longer use a separate counter, which resolves this issue.

* due to a bug in the Native POSIX Thread Library, in certain situations,"flush tables" caused a deadlock on tables that had a read lock. The mysqlddaemon had to be killed forcefully. Now, "COND_refresh" has been replacedwith "COND_global_read_lock", which resolves this issue.

* mysqld crashed if a query for an unsigned column type contained anegative value for a "WHERE [column] NOT IN" subquery.

* in the mysql client, empty strings were displayed as "NULL". Forexample, running "insert into [table-name] values (' ');" resulted in a"NULL" entry being displayed when querying the table using "select * from[table-name];".

* a bug in the optimizer code resulted in certain queries executing muchslower than expected.

* on 64-bit PowerPC architectures, MySQL did not calculate the thread stacksize correctly, which could have caused MySQL to crash when overly-complexqueries were used.

Note: these updated packages upgrade MySQL to version 5.0.45. For a fulllist of bug fixes and enhancements, refer to the MySQL release notes:http://dev.mysql.com/doc/refman/5.0/en/releasenotes-cs-5-0.html

All mysql users are advised to upgrade to these updated packages, whichresolve these issues.

4. Solution:

Before applying this update, make sure that all previously-releasederrata relevant to your system have been applied.

This update is available via Red Hat Network. Details on how to usethe Red Hat Network to apply this update are available athttp://kbase.redhat.com/faq/FAQ_58_10188