June 2007

ID: 143
Ref: 88/2007
Date: 30 June 2007:23:16:34
Version: 1

---

Title: iDefense Security Advisory 06.21.07 - Ingres Database Multiple Heap Corruption Vulnerabilities
Abstract: Remote exploitation of multiple heap overflow vulnerabilities in Ingres Database Server as distributed with Computer Associates International Inc. products may allow attackers to execute arbitrary code with SYSTEM privileges.
Vendors affected: Ingres

---

URL: http://labs.idefense.com/intelligence/vulnerabilities/

I. BACKGROUND

Ingres is the database backend used by default in several CA products.
The SCM (Secure Content Manager) is one of the products that uses Ingres.
The SCM use Ingres to store quarantined virii and blocked HTTP
requests/replies. For more information visit the following URLs.

http://www3.ca.com/solutions/Product.aspx?ID=1013

http://www.ingres.com/

II. DESCRIPTION

Remote exploitation of multiple heap overflow vulnerabilities in Ingres
Database Server as distributed with Computer Associates International
Inc.'s (CA) products may allow attackers to execute arbitrary code with
SYSTEM privileges.

The vulnerabilities exist in the Communications Server (iigcc.exe) and
Data Access Server (iigcd.exe) components of Ingres. The Communications
Server is the main component responsible for receiving and handling
requests from the network. The Data Access Server is responsible for
handling requests from the Ingres JDBC Driver and .NET data providers.
These requests are decoded into Ingres internal formats and passed on to
other components of the database server.

The application does not properly validate the length of attacker supplied
data before copying it into a fixed size heap buffer. This leads to an
exploitable condition.

III. ANALYSIS

Exploitation allows an unauthenticated attacker to execute arbitrary code
with SYSTEM privileges.

In order to exploit this vulnerability an attacker would have to send a
malformed request to the database server. This requires the ability to
establish a TCP session on port 10916 (iigcc) or 10923 (iigcd).

Exploitation has been demonstrated to be trivial.

IV. DETECTION

iDefense has confirmed the existence of this vulnerability in Ingres
Database 3.0.3 as included with CA eTrust Secure Content Manager r8 on
Windows. Previous versions may also be affected. In addition, any
application that uses the Ingres Database may be vulnerable.

V. WORKAROUND

Employing firewalls or other access control methods can effectively reduce
exposure to this vulnerability.

VI. VENDOR RESPONSE

CA has made fixes available for all supported CA products that embed
Ingres. For more information consult CA's Security Alert at the following
URL.

http://supportconnectw.ca.com/public/ca_common_docs/ingresvuln_letter.asp

VII. CVE INFORMATION

The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2007-3334 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

01/16/2007 Initial vendor notification
01/17/2007 Initial vendor response
06/21/2007 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 © 2007 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.

__________________________________________________________________________

CPNI values your feedback.

1. Which of the following most reflects the value of the advisory to you?
(Place an 'X' next to your choice)

Very useful:__ Useful:__ Not useful:__

2. If you did not find it useful, why not?


3. Any other comments? How could we improve our advisories?


Thank you for your contribution.
___________________________________________________________________________

CPNI wishes to acknowledge the contributions of iDefense for the
information contained in this advisory.
___________________________________________________________________________

This advisory contains information released by the original author. Some
of the information may have changed since it was released. If the issue
affects you, it may be prudent to retrieve the advisory from the site of
the original source to ensure that you receive the most current
information concerning that problem.

Reference to any specific commercial product, process, or service by trade
name, trademark manufacturer, or otherwise, does not constitute or imply
its endorsement, recommendation, or favouring by CPNI. The views and
opinions of authors expressed within this notice shall not be used for
advertising or product endorsement purposes.

CPNI shall not accept responsibility for any errors or omissions contained
within this advisory. In particular, they shall not be liable for any loss
or damage whatsoever, arising from or in connection with the usage of
information contained within this advisory.

CPNI is a member of the Forum of Incident Response and Security Teams
(FIRST) and has contacts with other international Incident Response Teams
(IRTs) in order to foster cooperation and coordination in incident
prevention, to prompt rapid reaction to incidents, and to promote
information sharing amongst its members and the community at large.
___________________________________________________________________________