search menu icon-carat-right cmu-wordmark

CERT Coordination Center

Oracle9i Application Server Apache PL/SQL module vulnerable to buffer overflow via cache directory name

Vulnerability Note VU#923395

Original Release Date: 2002-02-28 | Last Revised: 2002-03-15

Overview

A buffer overflow vulnerability exists in the Apache Procedural Language/Structured Query Language (PL/SQL) module used by Oracle9i Application Server (iAS). This vulnerability could allow an unauthenticated remote attacker to cause a denial-of-service or execute arbitrary code on the system with the privileges of the Apache process.

Description

NGSSoftware has released Insight Security Research Advisory #NISR06022002B that describes a number of vulnerabilities in the Apache PL/SQL module used by Oracle9i Application Server (iAS). This document addresses a buffer overflow vulnerability caused by a crafted cache directory name entered in the PL/SQL gateway configuration page.

Oracle iAS uses the Apache HTTP Server to provide web services, including access to stored procedures via the Oracle PL/SQL module (modpplsql or mod_plsql). In iAS, PL/SQL is used to communicate with the database and generate HTML that can be interpreted by a web browser. The PL/SQL module supports caching of PL/SQL objects and provides a web-based administration interface to configure the cache and other settings. A malformed directory name specified in the cache configuration form could trigger a buffer overflow, executing arbitrary code with the privileges of the Apache service. In the default configuration, the administration pages are available to anyone who is able to access to the web server [VU#611776].

The vulnerable PL/SQL module may also be used by Oracle9i Database and Oracle8i Database.

Impact

An unauthenticated remote attacker could cause a denial of service or execute arbitrary code on the system with the privileges of the Apache process. Since the Apache service typically runs with SYSTEM privileges on Windows NT and Windows 2000, an attacker may be able to gain complete control of the system.

Solution

Apply Patch
Apply the appropriate patch referenced in Oracle Security Alert #28.


Block or Restrict Access

Monitor and/or restrict access to the Apache HTTP service (typically 80/tcp). It may be possible to use TCP Wrapper or similar technology to provide improved access control and logging. Additionally, an application-level firewall or Intrusion Detection System (IDS) may be able to filter requests made to Apache.

Access to the PL/SQL gateway administration web pages can be restricted by specifying authorized user names and connect strings or an administrative Database Access Descriptor (DAD) in the PL/SQL gateway configuration file, /Apache/modplsql/cfg/wdbsvr.app. For more information, read the section titled Protecting the Administration pages in the Oracle iAS documentation underUsing the PL/SQL Gateway.

Note that these workarounds are designed to limit access and detect exploit attempts. These workarounds do not prevent exploitation of this vulnerability.

Disable Vulnerable Service

Disable the PL/SQL service (modplsql or mod_plsql in Apache).

Vendor Information

923395
 
Affected   Unknown   Unaffected

Oracle

Notified:  March 03, 2002 Updated:  March 05, 2002

Status

  Vulnerable

Vendor Statement

Oracle has released Oracle Security Alert #28.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us email.


CVSS Metrics

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A

References

Credit

The CERT Coordination Center thanks David Litchfield of NGSSoftware for information used in this document.

This document was written by Art Manion.

Other Information

CVE IDs: None
Severity Metric: 4.31
Date Public: 2002-02-06
Date First Published: 2002-02-28
Date Last Updated: 2002-03-15 20:21 UTC
Document Revision: 51

Sponsored by the Department of Homeland Security Office of Cybersecurity and Communications.