lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <47D5AA47.4010907@idefense.com>
Date: Mon, 10 Mar 2008 17:38:15 -0400
From: iDefense Labs <labs-no-reply@...fense.com>
To: vulnwatch@...nwatch.org, full-disclosure@...ts.grok.org.uk, 
	bugtraq@...urityfocus.com
Subject: iDefense Security Advisory 03.10.08: SAP MaxDB
 sdbstarter Privilege Escalation Vulnerability

iDefense Security Advisory 03.10.08
http://labs.idefense.com/intelligence/vulnerabilities/
Mar 10, 2008

I. BACKGROUND

SAP's MaxDB is a database software product. MaxDB was released as open
source from version 7.5 up to version 7.6.00. Later versions are no
longer open source but are available for download from the SAP SDN
website (sdn.sap.com) as a community edition with free community
support for public use beyond the scope of SAP applications. The
"sdbstarter" program is set-uid root and installed by default. For more
information, visit the product's website at the following URL.

https://www.sdn.sap.com/irj/sdn/maxdb

II. DESCRIPTION

Local exploitation of a design error in the "sdbstarter" program, as
distributed with SAP AG's MaxDB, could allow attackers to elevate
privileges to root.

This vulnerability exists due to a design error in the handling of
certain environment variables. These variables are used to specify the
configuration settings to be used by various MaxDB components. Since
the "sdbstarter" program honors these settings, an attacker can execute
arbitrary code with root privileges.

III. ANALYSIS

Exploitation allows an attacker to execute arbitrary code with root
privileges. To exploit this vulnerability, an attacker must be able to
execute the "sdbstarter" program. In a default installation, this
requires that the attacker be a member of the "sdba" group.

It is important to note that this vulnerability is not architecture
dependent. This vulnerability is trivially exploitable on any
Unix-based SAP MaxDB installation.

IV. DETECTION

iDefense has confirmed the existence of this vulnerability in SAP AG's
MaxDB version 7.6.0.37 on both Linux and Solaris. Other versions for
Unix-like systems are suspected to be vulnerable. Windows releases do
not include the "sdbstarter" program.

V. WORKAROUND

iDefense is currently unaware of any effective workaround for this
issue.

VI. VENDOR RESPONSE

SAP AG has addressed this vulnerability by releasing a new version of
MaxDB. For more information, consult SAP note 1140135.

VII. CVE INFORMATION

The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2008-0306 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org/), which standardizes names for
security problems.

VIII. DISCLOSURE TIMELINE

12/05/2007  Initial vendor notification
12/06/2007  Initial vendor response
03/10/2008  Coordinated public disclosure

IX. CREDIT

This vulnerability was discovered by Joshua J. Drake of VeriSign
iDefense Labs.

Get paid for vulnerability research
http://labs.idefense.com/methodology/vulnerability/vcp.php

Free tools, research and upcoming events
http://labs.idefense.com/

X. LEGAL NOTICES

Copyright © 2008 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 e-mail customerservice@...fense.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.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ