Ingres Database Buffer Overflow in 'libbecompat' Lets Local Users Gain Elevated Privileges
SecurityTracker Alert ID: 1020615|
SecurityTracker URL: http://securitytracker.com/id/1020615
(Links to External Site)
Date: Aug 3 2008
User access via local system|
Fix Available: Yes Vendor Confirmed: Yes |
Version(s): 2006 release 2 (9.1.0), 2006 release 1 (9.0.4), and 2.6|
A vulnerability was reported in Ingres Database. A local user can obtain elevated privileges on the target system.|
A local user can set a specially crafted environment variable to trigger a stack overflow in 'libbecompat' and execute arbitrary commands on the target system with 'ingres' user privileges.
The vendor was notified on July 20, 2007.
An anonymous researcher reported this vulnerability via iDefense.
A local user can obtain 'ingres' user privileges on the target system.|
The vendor has issued a fix.|
The vendor's advisory is available at:
Vendor URL: www.ingres.com/support/security-alert-080108.php (Links to External Site)
|Underlying OS: Linux (Any), UNIX (HP/UX)|
This archive entry has one or more follow-up message(s) listed below.|
Source Message Contents
Subject: iDefense Security Advisory 08.01.08: Ingres Database for Linux|
iDefense Security Advisory 08.01.08
Aug 01, 2008
Ingres Database is a database server used in several Computer
Associates' products. For example, CA Directory Service use thes Ingres
Database server. More information can be found on the vendor's website
at the following URL.
Local exploitation of a stack-based buffer overflow vulnerability in the
"libbecompat" library, as included in Ingres Database 2006 Release 2 for
Linux, allows attackers to execute arbitrary code with the privileges of
the Ingres user.
The vulnerability exists within the "libbecompat" library that is used
by several of the set-uid "ingres" utilities included with Ingres. When
copying a user supplied environment variable into a fixed-size stack
buffer, the library fails to check the length of the source string.
This results in an exploitable stack buffer overflow.
Exploitation of this vulnerability allows an attacker to execute
arbitrary code with the privileges of the "ingres" user. By itself,
this vulnerability does not have very serious consequences. However,
when combined with the library loading vulnerability, it allows an
attacker to execute arbitrary code with root privileges.
iDefense has confirmed the existence of this vulnerability in Ingres
2006 Enterprise Edition Release 2 for Linux x86 (32-bit). Other
versions may also be affected.
iDefense is currently unaware of any workaround for this issue.
VI. VENDOR RESPONSE
"This problem has been identified and resolved by Ingres in the
following releases: Ingres 2006 release 2 (9.1.0), Ingres 2006 release
1 (9.0.4), and Ingres 2.6."
For more information, refer to Ingres' advisory at the following URL.
VII. CVE INFORMATION
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2008-3389 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org/), which standardizes names for
VIII. DISCLOSURE TIMELINE
07/20/2007 Initial vendor response
07/23/2007 Initial vendor notification
08/01/2008 Coordinated public disclosure
The discoverer of this vulnerability wishes to remain anonymous.
Get paid for vulnerability research
Free tools, research and upcoming events
X. LEGAL NOTICES
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 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, this information.
To unsubscribe, go here: