search menu icon-carat-right cmu-wordmark

CERT Coordination Center


Oracle TNS Listener Control Utility (LSNRCTL) contains format string vulnerability

Vulnerability Note VU#301059

Original Release Date: 2002-06-04 | Last Revised: 2003-06-02

Overview

The Oracle Listener Control Utility (LSNRCTL) contains a format string vulnerability that could allow an unauthenticated, remote attacker to execute arbitrary code or commands or cause a denial of service.

Description

Oracle Transparent Network Substrate (TNS ) Listeners are processes that receive connection requests from clients and return information for the clients to use to make database connections. The Listener Control Utility (LSNRCTL) is used to administer Listeners, and has the ability to establish an Oracle Net connection to remote Listeners. When used to administer a Listener, the Listener Control Utility parses the Listener's configuration file ($ORACLE_HOME/NETWORK/ADMIN/LISTENER.ORA for the default Listener).

The Listener Control Utility contains a format string vulnerability that could be exploited when the utility parses commands that are supplied directly to it or read from a Listener configuration file. By default, unauthenticated users can control Oracle Listeners and modify their configuration files. By inserting crafted entries containing format string specifiers into a Listener configuration file, an attacker could cause the Listener Control Utility to execute arbitrary code or commands or crash the utility, preventing its use by legitimate users. An attacker with sufficient privileges can supply crafted commands containing format string specifiers directly to a vulnerable Listener Control Utility.

In one possible scenario, an attacker could modify a Listener configuration file and wait for a legitimate user, such as a database administrator (DBA), to run the Listener Control Utility. Any code or commands supplied by the attacker would execute with the privileges of the user who ran the Listener Control Utility.

Impact

An unauthenticated remote attacker could execute arbitrary code or commands or cause a denial of service on a vulnerable system.

Solution


Apply a Patch

Apply the appropriate patch as referenced in Oracle Security Alert #40.


Restrict Access to the Listener Control Utility

Restrict access to Oracle Listeners to trusted users, hosts, and networks. Use firewall or router access control lists (ACLs) to restrict connections to the port(s) used by Oracle Listeners, 1521/tcp by default. Enable the Oracle Net feature called "TCP valid node checking" by modifying $ORACLE_HOME/NETWORK/ADMIN/SQLNET.ORA ($ORACLE_HOME/NETWORK/ADMIN/PROTOCOL.ORA in Oracle8i and prior releases) as follows:

tcp.validnode_checking = YES
tcp.invited_nodes = {list of IP addresses}
tcp.excluded_nodes = {list of IP addresses}
Configure Oracle listeners with encrypted passwords.

Set more restrictive file permissions on Listener configuration files ($ORACLE_HOME/NETWORK/ADMIN/LISTENER.ORA for the default Listener).

Disable the runtime modification of Oracle listener parameters by modifying $ORACLE_HOME/NETWORK/ADMIN/LISTENER.ORA as follows:

ADMIN_RESTRICTIONS_listener_name=on
Note that these workarounds are designed to limit access; they may not prevent exploitation of this vulnerability.

Vendor Information

301059
Expand all

Oracle Corporation

Notified:  May 31, 2002 Updated:  September 17, 2002

Status

  Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

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

Addendum

Please see Oracle Security Alert #40.

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/CC thanks David Litchfield of NGSSoftware for information used in this document.

This document was written by Art Manion.

Other Information

CVE IDs: CVE-2002-0857
Severity Metric: 11.48
Date Public: 2002-05-27
Date First Published: 2002-06-04
Date Last Updated: 2003-06-02 19:06 UTC
Document Revision: 47

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