Date: Tue, 15 Apr 2008 18:17:57 -0400
From: iDefense Labs <labs-no-reply@idefense.com.>
To: [email protected], [email protected],
Subject: iDefense Security Advisory 04.09.08: IBM DB2 Universal Database Administration
Server File Creation Vulnerability
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: antivirus-gw at tyumen.ru
iDefense Security Advisory 04.09.08
http://labs.idefense.com/intelligence/vulnerabilities/
Apr 09, 2008
I. BACKGROUND
IBM Corp.'s DB2 Universal Database product is a large database server
product commonly used for high-end databases. The DB2 Administration
Server (DAS) implements the server component to which the Java-based
DB2 Control Center GUI connects. For more information, visit the
product website at the following URL.
http://ibm.com/db2/
II. DESCRIPTION
Local exploitation of a file creation vulnerability in the
Administration Server of IBM Corp.'s DB2 Universal Database allows
attackers to elevate privileges to root.
This vulnerability exists due to unsafe file access from within the
db2dasrrm program. When a user starts the DAS, the "db2dasrrm" process
is started with root privileges. As part of the initialization, the
"dasRecoveryIndex", "dasRecoveryIndex.tmp", ".dasRecoveryIndex.lock",
and "dasRecoveryIndex.cor" files are created with root privileges. By
removing and re-creating these files as symbolic links, an attacker can
create arbitrary files as root.
III. ANALYSIS
Exploitation allows local attackers to gain root privileges. In order to
exploit this vulnerability, an attacker must have access to an account
that is allowed to start and stop the DB2 Administration Server. For
example, the "dasusr1" account or an account with access to the
"db2adm1" group.
It should be noted that an attacker does not appear to any control over
the contents of the data written. However, this does not significantly
impact exploitation since the file is created using the user's umask
and group.
IV. DETECTION
iDefense has confirmed the existence of this vulnerability in IBM
Corp.'s DB2 Universal Database 9.1 release with Fix Pack 3 installed on
Linux. Other versions are also suspected to be vulnerable.
V. WORKAROUND
iDefense is currently unaware of any effective workaround for this
issue.
VI. VENDOR RESPONSE
IBM Corp. has addressed this vulnerability with the release of V9.1 Fix
Pack 4a, V8 FixPak 16, and V9.5 Fix Pack 1 of its Universal Database
product. More information can be found at the following URLs.
V8: http://www-1.ibm.com/support/docview.wss?uid=swg21256235
V9.1: http://www-1.ibm.com/support/docview.wss?uid=swg21255572
V9.5: http://www-1.ibm.com/support/docview.wss?uid=swg21287889
VII. CVE INFORMATION
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2007-5664 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org/), which standardizes names for
security problems.
VIII. DISCLOSURE TIMELINE
10/03/2007 Initial vendor notification
10/16/2007 Initial vendor response
04/09/2008 Coordinated public disclosure
IX. CREDIT
This vulnerability was discovered by Joshua J. Drake (iDefense Labs).
Get paid for vulnerability research
http://labs.idefense.com/methodology/vulnerability/vcp.php
Free tools, research and upcoming events
http://labs.idefense.com/
X. LEGAL NOTICES
Copyright ╘ 2008 iDefense, Inc.
Permission is granted for the redistribution of this alert
electronically. It may not be edited in any way without the express
written consent of iDefense. If you wish to reprint the whole or any
part of this alert in any other medium other than electronically,
please e-mail [email protected] for permission.
Disclaimer: The information in the advisory is believed to be accurate
at the time of publishing based on currently available information. Use
of the information constitutes acceptance for use in an AS IS condition.
There are no warranties with regard to this information. Neither the
author nor the publisher accepts any liability for any direct,
indirect, or consequential loss or damage arising from use of, or
reliance on, this information.
