summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'metadata/glsa/glsa-200409-02.xml')
-rw-r--r--metadata/glsa/glsa-200409-02.xml69
1 files changed, 69 insertions, 0 deletions
diff --git a/metadata/glsa/glsa-200409-02.xml b/metadata/glsa/glsa-200409-02.xml
new file mode 100644
index 000000000000..7eec2681ea8e
--- /dev/null
+++ b/metadata/glsa/glsa-200409-02.xml
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
+<glsa id="200409-02">
+ <title>MySQL: Insecure temporary file creation in mysqlhotcopy</title>
+ <synopsis>
+ The mysqlhotcopy utility can create temporary files with predictable paths,
+ allowing an attacker to use a symlink to trick MySQL into overwriting
+ important data.
+ </synopsis>
+ <product type="ebuild">MySQL</product>
+ <announced>2004-09-01</announced>
+ <revised count="01">2004-09-01</revised>
+ <bug>60744</bug>
+ <access>local</access>
+ <affected>
+ <package name="dev-db/mysql" auto="yes" arch="*">
+ <unaffected range="ge">4.0.20-r1</unaffected>
+ <vulnerable range="le">4.0.20</vulnerable>
+ </package>
+ </affected>
+ <background>
+ <p>
+ MySQL is a popular open-source multi-threaded, multi-user SQL database
+ server.
+ </p>
+ </background>
+ <description>
+ <p>
+ Jeroen van Wolffelaar discovered that the MySQL database hot copy utility
+ (mysqlhotcopy.sh), 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.
+ </p>
+ </description>
+ <impact type="normal">
+ <p>
+ 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.
+ </p>
+ </impact>
+ <workaround>
+ <p>
+ There is no known workaround at this time.
+ </p>
+ </workaround>
+ <resolution>
+ <p>
+ All MySQL users should upgrade to the latest version:
+ </p>
+ <code>
+ # emerge sync
+
+ # emerge -pv "&gt;=dev-db/mysql-4.0.20-r1"
+ # emerge "&gt;=dev-db/mysql-4.0.20-r1"</code>
+ </resolution>
+ <references>
+ <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0457">CAN-2004-0457</uri>
+ </references>
+ <metadata tag="requester" timestamp="2004-08-31T08:03:33Z">
+ jaervosz
+ </metadata>
+ <metadata tag="submitter" timestamp="2004-08-31T15:42:33Z">
+ koon
+ </metadata>
+</glsa>