blob: 6a5a63a89bada08cfac28b718f8847067d68eb0d [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200605-13">
<title>MySQL: Information leakage</title>
A MySQL server may leak information to unauthorized users.
<product type="ebuild">MySQL</product>
<announced>May 11, 2006</announced>
<revised>May 15, 2006: 04</revised>
<package name="dev-db/mysql" auto="yes" arch="*">
<unaffected range="ge">4.1.19</unaffected>
<unaffected range="rge">4.0.27</unaffected>
<vulnerable range="lt">4.1.19</vulnerable>
MySQL is a popular multi-threaded, multi-user SQL database server.
The processing of the COM_TABLE_DUMP command by a MySQL server fails to
properly validate packets that arrive from the client via a network
<impact type="low">
By crafting specific malicious packets an attacker could gather
confidential information from the memory of a MySQL server process, for
example results of queries by other users or applications. By using PHP
code injection or similar techniques it would be possible to exploit
this flaw through web applications that use MySQL as a database
Note that on 5.x versions it is possible to overwrite the stack and
execute arbitrary code with this technique. Users of MySQL 5.x are
urged to upgrade to the latest available version.
There is no known workaround at this time.
All MySQL users should upgrade to the latest version.
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=dev-db/mysql-4.0.27&quot;</code>
<uri link="">Original advisory</uri>
<uri link="">CVE-2006-1516</uri>
<uri link="">CVE-2006-1517</uri>
<metadata tag="requester" timestamp="Sat, 06 May 2006 16:33:38 +0000">
<metadata tag="submitter" timestamp="Mon, 08 May 2006 07:03:06 +0000">
<metadata tag="bugReady" timestamp="Mon, 08 May 2006 13:21:08 +0000">