Family: Slackware Local Security Checks --> Category: infos
SSA-2006-155-01 mysql Vulnerability Scan
Vulnerability Scan Summary
Detailed Explanation for this Vulnerability Test
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:
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 *)
Click HERE for more information and discussions on this network vulnerability scan.