Subject: iDEFENSE Security Advisory 01.13.05: MySQL MaxDB WebAgent websql logon Buffer Overflow Vulnerability
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 13 Jan 2005 17:43:52 -0500
Message-ID: <1CE07882ECEE894CA2D5A89B8DEBC4011CFDE3@porgy.admin.idefense.com.>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: iDEFENSE Security Advisory 01.13.05: MySQL MaxDB WebAgent websql logon Buffer Overflow Vulnerability
thread-index: AcT5wVqxzqHC7xQ9TfCnJ/cyKzDz3g==
From: "customer service mailbox" <customerservice@idefense.com.>
To: <bugtraq@securityfocus.com.>, <vulnwatch@vulnwatch.org.>
X-Virus-Scanned: antivirus-gw at tyumen.ru
MySQL MaxDB WebAgent websql logon Buffer Overflow Vulnerability
iDEFENSE Security Advisory 01.13.05
www.idefense.com/application/poi/display?id=3D181&type=3Dvulnerabilities
January 13, 2005
I. BACKGROUND
MaxDB by MySQL is a re-branded and enhanced version of SAP DB, SAP AG's
open source database. MaxDB is a heavy-duty, SAP-certified open source
database that offers high availability, scalability and a comprehensive
feature set. MaxDB complements the MySQL database server, targeted for
large mySAP ERP environments and other applications that require maximum
enterprise-level database functionality.
http://www.mysql.com/products/maxdb/
II. DESCRIPTION
Remote exploitation of a stack based buffer overflow vulnerability in=20
MySQL MaxDB could allow attackers to execute arbitrary code.=20
The vulnerability specifically exists due to a lack of bounds checking=20
in the websql CGI application. In this case, the value of the password=20
parameter is converted to unicode and then copied to the stack. The=20
resulting overflow can overwrite the saved values for eip and ebp if=20
supplied with a 294 byte value. The stored register values are=20
overwritten with portions of the unicode copy of the string which may be
leveraged to execute arbitrary code with SYSTEM privileges. A simple=20
overwrite with a long password value will result in the following=20
debugger output:
Program received signal SIGSEGV, Segmentation fault.
[Switching to thread 328.0xc80]
0x00410041 in ?? ()
(gdb) bt
#0 0x00410041 in ?? ()
#1 0x00410041 in ?? ()
#2 0x00420042 in ?? ()
#3 0x00430043 in ?? ()
#4 0x00440044 in ?? ()
(gdb) i r
eax 0x0 0
ecx 0x440044 4456516
edx 0x440044 4456516
ebx 0x1a789e0 27757024
esp 0x1559490 0x1559490
ebp 0x410041 0x410041
esi 0x1a72190 27730320
edi 0x1a3d2d4 27513556
eip 0x410041 0x410041
III. ANALYSIS
Successful exploitation of the vulnerability can allow remote attackers=20
to execute code with SYSTEM privileges. Note that the vulnerability is=20
in the web administration service which should be configured to not=20
allow connections from untrusted hosts or listen on public facing=20
network interfaces.
IV. DETECTION
iDEFENSE has confirmed the existence of this vulnerability in MySQL=20
MaxDB 7.5.00.
V. WORKAROUND
Employ firewalls, access control lists or other TCP/UDP restriction=20
mechanism to limit access to administrative systems and services.
VI. VENDOR RESPONSE
The vulnerability has been addressed in MaxDB 7.5.00.18.
Further details are available at:
http://www.sapdb.org/webpts?wptsdetail=3Dyes&ErrorType=3D0&ErrorID=3D1131=
190
VII. CVE INFORMATION
A Mitre Corp. Common Vulnerabilities and Exposures (CVE) number has not
been assigned yet.
VIII. DISCLOSURE TIMELINE
12/22/2004 Initial vendor notification
12/27/2004 Initial vendor response
01/13/2005 Public disclosure
IX. CREDIT
The discoverer of this vulnerability wishes to remain anonymous.
Get paid for vulnerability research
http://www.idefense.com/poi/teams/vcp.jsp
X. LEGAL NOTICES
Copyright (c) 2004 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
email [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.
