15817 : MySQL MaxDB Web Tool getLockTokenHeader() Function Remote Overflow
Printer | http://osvdb.org/15817 | Email This | Edit Vulnerability

Views This Week Views All Time Added to OSVDB Last Modified Modified (since 2008) Percent Complete
4 285 over 6 years ago about 1 year ago 2 times 100%

Timeline

Discovery Date Vendor Informed Date Vendor Ack Date Disclosure Date Vendor Solution Date
2005-03-08 2005-03-08 2005-03-11 2005-04-25 2005-04-25
Time to Patch Time to Vendor Response
48 days 3 days

Description

A remote overflow exists in MaxDB. MaxDB fails to perform adequate bounds checking in the WebDAV functionality of the web administration service tool resulting in a stack-based overflow. With a specially crafted HTTP request with the unlock method, along with a long Lock-Token string, a remote attacker can execute arbitrary code with SYSTEM privileges resulting in a loss of integrity.

Classification

Location: Remote / Network Access
Attack Type: Input Manipulation
Impact: Loss of Integrity
Exploit: Exploit Rumored
Disclosure: OSVDB Verified, Vendor Verified

Technical

MaxDB_ORG/sys/src/SAPDB/WebDAV/Handler/WDVHandler_CommonUtils.c:

WDVH_Bool getLockTokenHeader(sapdbwa_HttpRequestP request,
WDVH_Char *sLockToken,
WDVH_Char *errormsg)
{
WDVH_Char *temp1, *temp2, *temp4, *temp5;
WDVH_UInt4 length;
WDVH_Char temp3[WDVH_MAX_IF_HEADER_LEN];

if (request==NULL || sLockToken==NULL || errormsg==NULL)
return WDVH_False;

temp4 = (char*)sapdbwa_GetHeader(request,"Lock-Token");
if (temp4 != NULL) {
strcpy(temp3,temp4);
[...]

The variable temp3 is a fixed-length stack buffer. The function sapdbwa_GetHeader() returns the user supplied value for Lock-Token. This user-supplied value is then copied into the fixed-size buffer using a strcpy() call. Due to no boundary checking, it is possible to overflow the stack buffer and overwrite stack memory, ultimately leading to control of execution flow and execution of arbitrary code.

Solution

Upgrade to version 7.5.00.26 or higher, as it has been reported to fix this vulnerability. It is also possible to correct the flaw by implementing the following workaround(s): The vulnerability is in the web administration service, which should be configured to not allow connections from untrusted hosts or listening on public-facing network interfaces.

Products

MySQL AB
Watch-list
MaxDB
Watch-list
7.5.00.23
7.5.00.26

References

Tools & Filters

Snort

11196 15951

Credit

CVSSv2 Score

CVSSv2 Base Score = 10.0
Source: nvd.nist.gov | Generated: 2005-06-09 | Disagree?

Access_vector_2 Access_complexity_2 Authentication_2 Confidentiality_impact_2 Integrity_impact_2 Availability_impact_2

Blogs

This section lists the latest news and blogs found via the daylife API (and for older items, the technorati API), which mention or otherwise discuss this vulnerability.

None found at this time

Comments

No Comments.

The database information may change without any notice. Use of the information constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the copyright holder or distributor (OSVDB or OSF) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.

© Copyright 2012 Open Source Vulnerability Database (OSVDB), All Rights Reserved.
Privacy Statement - Terms of Use