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.
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 improper handling of HTTP
GET queries containing a percent sign (%). When an attacker issues an
HTTP GET request specifying a percent sign followed by a long string as
the file parameter, a stack-based overflow occurs. Although exceptions
within the process can be raised with smaller strings, it is necessary
to provide a string of approximately 4,000 bytes in length to overwrite
the process Structured Exception Handler (SEH). Using this method, is
possible to gain control of execution flow and execute arbitrary code.
It is also possible to simply overwrite the program's saved instruction
pointer. However, it would be necessary to provide several valid
pointers in the buffer along the way in order to avoid premature
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 not to
allow connections from untrusted hosts or listen on public-facing
iDEFENSE has confirmed the existence of this vulnerability in MySQL
Employ firewalls, access control lists or other TCP/UDP restriction
mechanism to limit access to administrative systems and services.
This vulnerability is addressed in MySQL MaxDB 7.5.00.26 available for
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CAN-2005-0684 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org), which standardizes names for
security problems. This is one of two vulnerabilities that have been
03/08/2005 Initial vendor notification
03/11/2005 Initial vendor response
04/25/2005 Coordinated public disclosure
The discoverer of this vulnerability wishes to remain anonymous.
Get paid for vulnerability research
Copyright © 2005 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 email@example.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,