Vulnerability Note VU#936868

Oracle Database Server contains stack overflow in logging mechanism when supplied overly long library name

Original Release date: 28 Jul 2003 | Last revised: 12 Sep 2003

Overview

There is a buffer overflow in several versions of Oracle Database. The impact of this vulnerability may include the execution of arbitrary code; the ability to read, modify, or delete information stored in underlying Oracle databases; and denial of service.

Description

A buffer overflow exists in Oracle9i Release 2, Oracle9i Release 1, and multiple versions of Oracle8i. For more detailed information on versions affected, please see Oracle Security Alert 57. The buffer overflow exists in a portion of code designed to log attempts to exploit a previously discovered vulnerability, described here:

The newly discovered buffer overflow is described in the following documents:
It is important to note that a discrepancy existed between these two documents. Specifically, the Oracle Alert asserted that only an authenticated user with privileges would be able to exploit this vulnerability. Quoting from Oracle Security Alert #29:

Risk to exposure is low, as the CREATE LIBRARY or the CREATE ANY LIBRARY privilege is needed to exploit these vulnerabilities.
On the other hand, the NGSSoftware Advisory asserts an unauthenticated remote attacker can exploit the vulnerability. Quoting from NGSSoftware Advisory #NISR25072003:

As this does not require a user ID or password it must be stressed that this is a critical vulnerability.
This discrepancy is being discussed in a public forum, too:

Tina Bird's Post - <http://www.securityfocus.com/archive/1/330529>
David Litchfield's Response - <http://www.securityfocus.com/archive/1/330566>
On 09/04/2003 Oracle Security Alert 57 was updated to read "These potential vulnerabilities can be exploited in some cases without a username and password."

Impact

An intruder who exploits this vulnerability can remotely execute arbitrary code. On UNIX systems, this code runs as the 'oracle' user. From there, it is likely that an intruder could leverage that access to gain additional control over the system. If running on Windows systems, the intruder's code will run in the Local System security context. In either case, the data contained in the database is at risk.

Solution

Apply a patch, as described in Oracle Security Alert 57. Note that Oracle has indicated the following in their security alert, "Currently, due to architectural constraints, there are no plans to release a patch for versions 9.0.1.4, 8.1.7.4, 8.1.6.x, 8.1.5.x, 8.0.6.3, 8.0.5.x, 7.3.x, or other patchsets of the supported releases."

Workaround

Until you can apply a patch, you may wish to follow the advice outlined in David Litchfield's Bugtraq post:

Alternatively customers can disable external procedure functionality. To do this edit the listener.ora file, removing the entries for extproc, and also delete the extproc binary which can be found in $ORACLE_HOME/bin.
It is important to understand your service requirements before deciding what changes are appropriate.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
Oracle CorporationAffected-25 Jul 2003
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

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

References

Credit

This vulnerability was discovered by David Litchfield and Chris Anley of NGSSoftware Insight Security Research .

This document was written by Ian A Finlay.

Other Information

  • CVE IDs: Unknown
  • Date Public: 25 Jul 2003
  • Date First Published: 28 Jul 2003
  • Date Last Updated: 12 Sep 2003
  • Severity Metric: 31.64
  • Document Revision: 31

Feedback

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