Difference between revisions of "Testing for DB Listener (OWASP-CM-002)"

Jump to: navigation, search
(Black Box testing and example)
Line 87: Line 87:
TNS Listener tool (Perl) - http://www.jammed.com/%7Ejwa/hacks/security/tnscmd/tnscmd-doc.html<br>
* TNS Listener tool (Perl) - http://www.jammed.com/%7Ejwa/hacks/security/tnscmd/tnscmd-doc.html<br>
Toad for Oracle - http://www.quest.com/toad
* Toad for Oracle - http://www.quest.com/toad
{{Category:OWASP Testing Project AoC}}
{{Category:OWASP Testing Project AoC}}

Revision as of 12:09, 17 November 2006

OWASP Testing Guide v2 Table of Contents

Brief Summary

The Data base listener is a network daemon unique to Oracle databases. It waits for connection requests from remote clients. This daemon can be compromised and hence affect the availability of the database.

Description of the Issue

The DB listener is the entry point for remote connections to an Oracle database. It listens for connection requests and handles them accordingly. This test is possible, if the tester can access to this service: that means the test will be done from the Intranet (in normal Oracle installation this service is not exposed to the external network...we hope so!) The listener by default listens on port 1521, it is good practice to change the listener from this port to another arbitary port number.
If this listener is "turned off" remote acess to the database is not possible. If this is the case ones application would fail also creating a denial of service attack.
Potential areas of attack:

  • Stop the Listener - Hence creating a DoS attack.
  • Set a password and prevent others from controlling the Listener - Hijack the DB.
  • Write trace and log files to any file accessible to the process owner of tnslnsr (usually Oracle) - Possible information leakage.
  • Obtain detailed information on the Listener, database, and application configuration.

Black Box testing and example

Upon discovering the port on which the listener resides one can assess the listener by running a tool developed by Integrigy:

Listener Test.JPG

The tool above checks the following:
Listener Password On many Oracle systems the listener password may not be set. The tool above verifies this. If the password is not set an attacker could set the password and hijack the listener, albeit the password can be removed by locally editing the Listener.ora file.

Enable Logging The tool above also tests to see if logging has been enabled. If it has not one would not detect any change to the listener/or have a record of it and also detection of brute force attacks on the listener would not be audited.

Admin Restrictions If Admin restrictions are not enabled it is possible to use the "SET" commands remotley.

If you find a TCP/1521 open port on a server, maybe you have an Oracle Listener that accept connections from the outside. If the listener is not protected by an authentication mechanism, or you can find easily a credential (as said above), it is possible to exploit this vulnerability to enumerate the Oracle services. For example, using LSNRCTL(.exe) (contained in every Client Oracle installation), you can obtain the following output:

TNSLSNR for 32-bit Windows: Version - Production
TNS for 32-bit Windows: Version - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version - Production
Windows NT Named Pipes NT Protocol Adapter for 32-bit Windows: Version - Production
Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version - Production,,

The Oracle Listener permits to enumerate default users on Oracle Server:

Username	Password
OUTLN	            OUTLN

In this case, we have not founded privileged DBA accounts, but OUTLN and BACKUP accounts hold a foundamental privilege: EXECUTE ANY PROCEDURE. That means that it is possible to execute every procedures, for exemple the following:

exec dbms_repcat_admin.grant_admin_any_schema('BACKUP');

The execution of this command permit to obtain DBA privileges. Now the user can interact directly with the DB and execute for example:

select * from session_privs ;

The output is the following screenshot:


So the user can now execute a lot of operations, in particular: DELETE ANY TABLE DROP ANY TABLE.

Gray Box testing and example

Testing for Topic X vulnerabilities:
Result Expected:



OWASP Testing Guide v2

Here is the OWASP Testing Guide v2 Table of Contents