[slackware-security] mysql

New mysql packages are available for Slackware 10.2 and -current to
fix security issues. The MySQL package shipped with Slackware 10.2
may possibly leak sensitive information found in uninitialized
memory to authenticated users. The MySQL package previously in
Slackware -current also suffered from these flaws, but an additional
overflow could allow arbitrary code execution.

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.
Issues that affect both Slackware 10.2 and -current:
https://vulners.com/cve/CVE-2006-1516
https://vulners.com/cve/CVE-2006-1517

An issue affecting only Slackware -current:
https://vulners.com/cve/CVE-2006-1518

Here are the details from the Slackware 10.2 ChangeLog:

patches/packages/mysql-4.1.19-i486-1.tgz:
Upgraded to mysql-4.1.19.
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 information, see:
https://vulners.com/cve/CVE-2006-1516
https://vulners.com/cve/CVE-2006-1517
(* Security fix *)

Here are the details from the Slackware -current ChangeLog:

ap/mysql-5.0.21-i486-1.tgz: Upgraded to mysql-5.0.21.
This fixes some security issues, including possible information leakage, and
execution of arbitrary code. 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 information, see:
https://vulners.com/cve/CVE-2006-1516
https://vulners.com/cve/CVE-2006-1517
https://vulners.com/cve/CVE-2006-1518
(* Security fix *)

Where to find the new packages:

Updated package for Slackware 10.2:
ftp://ftp.slackware.com/pub/slackware/slackware-10.2/patches/packages/mysql-4.1.19-i486-1.tgz

Updated package for Slackware -current:
ftp://ftp.slackware.com/pub/slackware/slackware-current/slackware/ap/mysql-5.0.21-i486-1.tgz

MD5 signatures:

Slackware 10.2 package:
c229e19d782404da119be46355a170d2 mysql-4.1.19-i486-1.tgz

Slackware -current package:
51008b23954c0d82c2670290476d0249 mysql-5.0.21-i486-1.tgz

Installation instructions:

Upgrade the package as root:
> upgradepkg mysql-4.1.19-i486-1.tgz

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