DATE: [ GLSA 200605-13 MySQL: Information leakage
Posted on: 05/16/2006 10:12 PM

A new security update has been released for Gentoo Linux - MySQL: Information leakage. Here the announcement:

Gentoo Linux Security Advisory [UPDATE] GLSA 200605-13:04
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Severity: Low
Title: MySQL: Information leakage
Date: May 11, 2006
Updated: May 15, 2006
Bugs: #132146
ID: 200605-13:04

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Update
======

For a short time version 4.0.27 was incorrectly listed as vulnerable
and the resolution incorrectly forced an upgrade to 4.1.x for 4.0.x users.

The updated sections appear below.

Affected packages
=================

-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 dev-db/mysql lt; 4.1.19 gt;= 4.1.19
*gt;= 4.0.27

Resolution
==========

All MySQL users should upgrade to the latest version.

# emerge --sync
# emerge --ask --oneshot --verbose "gt;=dev-db/mysql-4.0.27"

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

http://security.gentoo.org/glsa/glsa-200605-13.xml

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
http://bugs.gentoo.org.

License
=======

Copyright 2006 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

http://creativecommons.org/licenses/by-sa/2.5



Printed from Linux Compatible (http://www.linuxcompatible.org/news/story/date_glsa_200605_13_mysql_information_leakage.html)