full-disclosure-uk August 2008 archive
Main Archive Page > Month Archives  > full-disclosure-uk archives
full-disclosure-uk: [Full-disclosure] iDefense Security Advisory

[Full-disclosure] iDefense Security Advisory 08.01.08: Ingres Database for Linux ingvalidpw Untrusted Library Path Vulnerability

From: iDefense Labs <labs-no-reply_at_nospam>
Date: Sat Aug 02 2008 - 04:30:27 GMT
To: vulnwatch@vulnwatch.org, full-disclosure@lists.grok.org.uk, bugtraq@securityfocus.com


iDefense Security Advisory 08.01.08
http://labs.idefense.com/intelligence/vulnerabilities/ Aug 01, 2008

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

http://ingres.com/downloads/prod-cert-download.php

II. DESCRIPTION Local exploitation of an untrusted library path vulnerability in the
"ingvalidpw" utility, as included in Ingres Database 2006 Release 2 for
Linux, allows attackers to execute arbitrary code with root privileges.

The vulnerability exists within the "ingvalidpw" utility included with Ingres database. This utility is used to verify a user's credentials, and is installed set-uid root. When loading shared libraries, the
"ingvalidpw" program will load libraries from a directory owned by the
"ingres" user. By using a specially crafted library, a user with
"ingres" privileges can gain root.

III. ANALYSIS Exploitation of this vulnerability allows an attacker to elevate their privileges from the "ingres" user to root. By itself, this is not that serious of a vulnerability. However, when combined with the libbecompat and verifydb vulnerabilities it allows an unprivileged local user to gain root privileges.

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

V. WORKAROUND iDefense is currently unaware of any workarounds 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.

http://www.ingres.com/support/security-alert-080108.php

VII. CVE INFORMATION The Common Vulnerabilities and Exposures (CVE) project has assigned the name CVE-2008-3357 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 07/20/2007 Initial vendor response 07/23/2007 Initial vendor notification 08/01/2008 Coordinated public disclosure

IX. CREDIT The discoverer of this vulnerability wishes to remain anonymous.

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@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.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/