ID SSA-2006-155-01
Type slackware
Reporter Slackware Linux Project
Modified 2006-06-05T01:12:48


New mysql packages are available for Slackware 9.1, 10.0, 10.1, 10.2 and -current to fix security issues.

The MySQL packages shipped with Slackware 9.1, 10.0, and 10.1 may possibly leak sensitive information found in uninitialized memory to authenticated users. This is fixed in the new packages, and was already patched in Slackware 10.2 and -current. Since the vulnerabilities require a valid login and/or access to the database server, the risk is moderate. Slackware does not provide network access to a MySQL database by default.

More details about the issues may be found in the Common Vulnerabilities and Exposures (CVE) database. Fixes that affect Slackware 9.1, 10.0, and 10.1:

The MySQL packages in Slackware 10.2 and -current have been upgraded to MySQL 4.1.20 (Slackware 10.2) and MySQL 5.0.22 (Slackware -current) to fix an SQL injection vulnerability.

For more details, see the MySQL 4.1.20 release announcement here: And the MySQL 5.0.22 release announcement here: The CVE entry for this issue can be found here:

Here are the details from the Slackware 10.1 ChangeLog:

patches/packages/mysql-4.0.27-i486-1_slack10.1.tgz: Upgraded to mysql-4.0.27. This fixes some minor security issues with possible information leakage. Note that the information leakage bugs require that the attacker have access to an account on the database. Also note that by default, Slackware's rc.mysqld script does not allow access to the database through the outside network (it uses the --skip-networking option). If you've enabled network access to MySQL, it is a good idea to filter the port (3306) to prevent access from unauthorized machines. For more details, see the MySQL 4.0.27 release announcement here: For more information, see: ( Security fix )

Here are the details from the Slackware 10.2 ChangeLog:

patches/packages/mysql-4.1.20-i486-1_slack10.2.tgz: Upgraded to mysql-4.1.20. This fixes an SQL injection vulnerability. For more details, see the MySQL 4.1.20 release announcement here: The CVE entry for this issue will be found here:

Where to find the new packages:

HINT: Getting slow download speeds from Give a try. This is another primary FTP site for Slackware that can be considerably faster than downloading from

Thanks to the friendly folks at the OSU Open Source Lab ( for donating additional FTP and rsync hosting to the Slackware project! :-)

Also see the "Get Slack" section on for additional mirror sites near you.

Updated package for Slackware 9.1:

Updated package for Slackware 10.0:

Updated package for Slackware 10.1:

Updated package for Slackware 10.2:

Updated package for Slackware -current:

MD5 signatures:

Slackware 9.1 package: eea73f16715c07de52701b67f037e7ab mysql-4.0.27-i486-1_slack9.1.tgz

Slackware 10.0 package: 6afab2cdd09adf4b4f822db6c74b167e mysql-4.0.27-i486-1_slack10.0.tgz

Slackware 10.1 package: cbe2044d3b75606de6f3796d607e7c0a mysql-4.0.27-i486-1_slack10.1.tgz

Slackware 10.2 package: 249bc3f4610cbedf8b0a6fc64c28c53f mysql-4.1.20-i486-1_slack10.2.tgz

Slackware -current package: af1829c54b901bc01fcd269f27580b21 mysql-5.0.22-i486-1.tgz

Installation instructions:

Upgrade the package as root: > upgradepkg mysql-4.1.20-i486-1_slack10.2.tgz

Then, restart the database server: > sh /etc/rc.d/rc.mysqld restart