blob: 4cb3ac353075cf515220a3a00c38eb15bcac29ec [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200501-33">
<title>MySQL: Insecure temporary file creation</title>
MySQL is vulnerable to symlink attacks, potentially allowing a local user
to overwrite arbitrary files.
<product type="ebuild">mysql</product>
<announced>January 23, 2005</announced>
<revised>January 23, 2005: 01</revised>
<package name="dev-db/mysql" auto="yes" arch="*">
<unaffected range="ge">4.0.22-r2</unaffected>
<vulnerable range="lt">4.0.22-r2</vulnerable>
MySQL is a fast, multi-threaded, multi-user SQL database server.
Javier Fernandez-Sanguino Pena from the Debian Security Audit
Project discovered that the 'mysqlaccess' script creates temporary
files in world-writeable directories with predictable names.
<impact type="normal">
A local attacker could create symbolic links in the temporary
files directory, pointing to a valid file somewhere on the filesystem.
When the mysqlaccess script is executed, this would result in the file
being overwritten with the rights of the user running the software,
which could be the root user.
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.22-r2&quot;</code>
<uri link="">CAN-2005-0004</uri>
<uri link="">Secunia Advisory SA13867</uri>
<metadata tag="requester" timestamp="Wed, 19 Jan 2005 10:01:33 +0000">
<metadata tag="bugReady" timestamp="Fri, 21 Jan 2005 22:17:35 +0000">
<metadata tag="submitter" timestamp="Sat, 22 Jan 2005 01:00:40 +0000">