MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:Kent Boortz Date:May 12 2006 4:44pm
Subject:MySQL 4.0.27 has been released - Security Update
View as plain text  

MySQL 4.0.27, a new version of the popular Open Source Database
Management System, has been released. The Community Edition is now
available in source and binary form for a number of platforms from our
download pages at

and mirror sites.

This is a security fix release and bugfix release for the 4.0
production release family.

This MySQL 4.0.27 release includes the patches for recently reported
security vulnerabilities in the MySQL client-server protocol. We would
like to thank Stefano Di Paola <stefano.dipaola@stripped> for finding
and reporting these to us.

Functionality added or changed:

   * The MySQL-server RPM now explicitly assigns the mysql system
     user to the mysql user group during the post-installation
     process. This corrects an issue with upgrading the server on
     some Linux distributions whereby a previously existing mysql
     user was not changed to the mysql group, resulting in wrong
     groups for files created following the installation.

   * Better detection of connection timeout for replication servers
     on Windows allows elimination of extraneous Lost connection
     errors in the error log.

Bugs fixed:

   * Security fix: A malicious client, using specially crafted
     invalid login or COM_TABLE_DUMP packets was able to read
     uninitialized memory, which potentially, though unlikely in
     MySQL, could have led to an information disclosure.
     Thanks to Stefano Di Paola stefano.dipaola@stripped for
     finding and reporting this bug.

   * MySQL-shared-compat-4.0.26-0.i386.rpm and 4.0.27 incorrectly
     depend on glibc 2.3 and cannot not be installed on a glibc 2.2
     system. For MySQL 4.0, we recommend using the older
     MySQL-shared-compat-4.0.25-0.i386.rpm package.

   * When myisamchk needed to rebuild a table, AUTO_INCREMENT
     information was lost. (Bug#10405:

   * BIT_COUNT() could return an incorrect value for right table
     columns in a LEFT JOIN.

   * An UPDATE statement which tried to update a column with a name
     beginning with an asterisk would cause the server to crash.
     This was because the MySQL server would wrongly expand the '*'
     character to the list of all table columns, causing the list of
     columns to become longer than the list of values. Now the server
     performs this expansion only if the '*' character is followed
     by a space. (Bug#15610:

   * An INSERT ... SELECT statement between tables in a MERGE set
     can return errors when statement involves insert into child
     table from merge table or vice-versa.

   * A LIMIT-related optimization failed to take into account that
     MyISAM table indexes can be disabled, causing Error 124 when
     it tried to use such an index.

   * For a table that had been opened with HANDLER OPEN, issuing
     crash. (Bug#14397:

   * Queries of the form (SELECT ...) ORDER BY ... were being
     treated as a UNION. This improperly resulted in only distinct
     values being returned (because UNION by default eliminates
     duplicate results). Also, references to column aliases in
     ORDER BY clauses following parenthesized SELECT statements
     were not resolved properly.

   * SELECT DISTINCT with a GROUP BY clause caused a server crash.

   * SHOW CREATE TABLE did not display any FOREIGN KEY clauses if a
     temporary file could not be created. Now SHOW CREATE TABLE
     displays an error message in an SQL comment if this occurs.

   * MySQL programs in binary distributions for Solaris 8/9/10 x86
     systems would not run on Pentium III machines.

   * Queries against a MERGE table that has a composite index could
     produce incorrect results.

   * The counters for the Key_read_requests, Key_reads,
     Key_write_requests, and Key_writes status variables were
     changed from "unsigned long" to "unsigned long long" to
     accommodate larger values before the variables
     roll-over and restart from 0.

   * A concurrency problem for CREATE ... SELECT could cause a
     server crash. (Bug#12845:

   * On HP-UX 11.x (PA-RISC), the -L option caused "mysqlimport" to
     crash. (Bug#12958:

   * The server crashed when one thread resized the query cache
     while another thread was using it.

Bugs fixed (for problems building from source):

   * Avoid trying to include <asm/atomic.h> when it doesn't work
     in C++ code. (Bug#13621:

   * MySQL would not compile on Linux distributions that use the
     "tinfo" library. (Bug#18912:

   * Fixed problems with static variables to allow building on
     Fedora Core 3. (Bug#6554:


Kent Boortz, Senior Software Developer
Office: +46 18 174400 ext. 4450 (VoIP)
Office: +46 19 182931
Mobile: +46 70 2791171
MySQL 4.0.27 has been released - Security UpdateKent Boortz12 May