// back

MySQL MaxDB WebAgent websql logon Buffer Overflow Vulnerability

01.13.05

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/

DESCRIPTION

Remote exploitation of a stack based buffer overflow vulnerability in
MySQL MaxDB could allow attackers to execute arbitrary code.

The vulnerability specifically exists due to a lack of bounds checking
in the websql CGI application. In this case, the value of the password
parameter is converted to unicode and then copied to the stack. The
resulting overflow can overwrite the saved values for eip and ebp if
supplied with a 294 byte value. The stored register values are
overwritten with portions of the unicode copy of the string which may be
leveraged to execute arbitrary code with SYSTEM privileges. A simple
overwrite with a long password value will result in the following
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

ANALYSIS

Successful exploitation of the vulnerability can allow remote attackers
to execute code with SYSTEM privileges. Note that the vulnerability is
in the web administration service which should be configured to not
allow connections from untrusted hosts or listen on public facing
network interfaces.

DETECTION

iDEFENSE has confirmed the existence of this vulnerability in MySQL
MaxDB 7.5.00.

WORKAROUND

Employ firewalls, access control lists or other TCP/UDP restriction
mechanism to limit access to administrative systems and services.

VENDOR RESPONSE

The vulnerability has been addressed in MaxDB 7.5.00.18.

Further details are available at:
http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1131190

CVE INFORMATION

The Common Vulnerabilities and Exposures (CVE) project has assigned the
names CAN-2005-0111 to these issues. This is a candidate for inclusion
in the CVE list (http://cve.mitre.org), which standardizes names for
security problems.

DISCLOSURE TIMELINE

12/22/2004   Initial vendor notification
12/27/2004   Initial vendor response
01/13/2005   Public disclosure

CREDIT

The discoverer of this vulnerability wishes to remain anonymous.

Get paid for vulnerability research
http://www.idefense.com/poi/teams/vcp.jsp

LEGAL NOTICES

Copyright © 2004 Verisign, 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 customerservice@idefense.com 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.