MySQL MaxDB Web Agent WebDBM Server Name Denial of Service Vulnerability

iDEFENSE Security Advisory 10.06.04a:
www.idefense.com/application/poi/display?id=150&type=vulnerabilities
October 6, 2004

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.

II. DESCRIPTION

Remote exploitation of an input validation error in MySQL MaxDB could
allow attackers to trigger a denial of service condition.

The problem specifically exists due to improper input validation of a
user-supplied variable in the IsAscii7() function. Remote attackers can
send a specially crafted HTTP request to webdbm with the 'Server' value
containing ASCII values above 0x7F to cause an assert directive to fail,
resulting in a DoS condition.

    wahttp:
    ToolsCommon/Tools_DynamicUTF8String.hpp:249:
    Tools_DynamicUTF8String::Tools_DynamicUTF8String(const SAPDB_Char *)
    Assertion `IsAscii7(src)' failed.

    Program received signal SIGABRT, Aborted.
    [Switching to Thread 10251 (LWP 12706)]
    0x40429781 in kill () from /lib/libc.so.6

III. ANALYSIS

Successful exploitation allows remote attackers to trigger a denial of
service condition on the web agent component of MaxDB.

IV. DETECTION

iDEFENSE has confirmed that SAP DB version 7.5 for both Linux and
Windows is vulnerable.

V. WORKAROUND

Use of an ingress perimeter firewall filter can help detect and mitigate
the risk of attack.

VI. VENDOR RESPONSE

"A solution for the issue is available with MaxDB 7.5.00.18."

VII. CVE INFORMATION

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

VIII. DISCLOSURE TIMELINE

08/16/2004   Initial vendor notification
08/16/2004   iDEFENSE clients notified
08/19/2004   Initial vendor response
10/06/2004   Coordinated public disclosure

IX. CREDIT

Patrik Karlsson (cqure.net) is credited with this discovery.

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 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.

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html