Vulnerability Note VU#105259

Oracle Database Server vulnerable to DoS via repeated requests to Oracle listener without connecting to redirected port

Original Release date: 08 Dec 2001 | Last revised: 14 Jan 2004

Overview

Oracle Database Server may consume all available memory and crash if clients do not connect completely in the expected manner.

Description

When a connection request is made to Oracle for Windows NT, Oracle Database Server creates a new thread listening on a new port and redirects the connection to the new port. This new thread remains in memory listening until the client connects to its port or the Oracle Database Server is restarted.

Impact

By making many connection requests to Oracle without connecting to the new threads created to handle the connections, an attacker can force the server to consume all memory with listening threads. Once all server memory is consumed, the next console login attempt will crash the server.

Solution

The CERT/CC is currently unaware of a practical solution to this problem.

Enable tcp.validnode_checking and set tcp.invited_nodes and tcp.excluded_nodes to limit Oracle access to trusted hosts.

Set the following parameters in the Oracle Net8 configuration file PROTOCOL.ORA:

    tcp.validnode_checking = YES
    tcp.invited_nodes = {list of IP addresses}
    tcp.excluded_nodes = {list of IP addresses}

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
Oracle CorporationAffected27 Aug 200117 Nov 2001
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

Thanks to Internet Security Systems (ISS) for their advisory on this issue.

This document was written by Shawn Van Ittersum.

Other Information

  • CVE IDs: CVE-2001-0513
  • Date Public: 19 Jun 2001
  • Date First Published: 08 Dec 2001
  • Date Last Updated: 14 Jan 2004
  • Severity Metric: 3.02
  • Document Revision: 17

Feedback

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