blob: a042b03bc275c5453fff087570ee5bda0f25a714 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200409-02">
<title>MySQL: Insecure temporary file creation in mysqlhotcopy</title>
The mysqlhotcopy utility can create temporary files with predictable paths,
allowing an attacker to use a symlink to trick MySQL into overwriting
important data.
<product type="ebuild">MySQL</product>
<announced>September 01, 2004</announced>
<revised>September 01, 2004: 01</revised>
<package name="dev-db/mysql" auto="yes" arch="*">
<unaffected range="ge">4.0.20-r1</unaffected>
<vulnerable range="le">4.0.20</vulnerable>
MySQL is a popular open-source multi-threaded, multi-user SQL database
Jeroen van Wolffelaar discovered that the MySQL database hot copy utility
(, when using the scp method, uses temporary files with
predictable names. A malicious local user with write access to the /tmp
directory could create a symbolic link pointing to a file, which may then
be overwritten. In cases where mysqlhotcopy is run as root, a malicious
user could create a symlink to a critical file such as /etc/passwd and
cause it to be overwritten.
<impact type="normal">
A local attacker could use this vulnerability to destroy other users' data
or corrupt and destroy system files, possibly leading to a denial of
service condition.
There is no known workaround at this time.
All MySQL users should upgrade to the latest version:
# emerge sync
# emerge -pv ">=dev-db/mysql-4.0.20-r1"
# emerge ">=dev-db/mysql-4.0.20-r1"</code>
<uri link="">CAN-2004-0457</uri>
<metadata tag="requester" timestamp="Tue, 31 Aug 2004 08:03:33 +0000">
<metadata tag="submitter" timestamp="Tue, 31 Aug 2004 15:42:33 +0000">