The Data base listener is a network daemon unique to Oracle databases. It waits for connection requests from remote clients.

+

The database (DB) 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.

+

This daemon can sometimes be compromised and hence can affect the availability of the database or the validity of data stored within it.

== Description of the Issue ==

== 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 should be done from the Intranet (major Oracle installation don't expose this service to the external network).

+

The DB listener is the entry point for remote connections to an Oracle database. It listens for connection requests and handles them accordingly. The testing outlined in this section is possible if the tester can access this service -- the test should be done from the Intranet (major Oracle installations don't expose this service to the external network).

−

The listener by default listens on port 1521, it is good practice to change the listener from this port to another arbitary port number.

+

The listener, by default, listens on port 1521 (port 2483 is the new officially registered port for the TNS Listener and 2484 for the TNS Listener using SSL). It is a good practice to change the listener from this port to another arbitrary port number.

−

<BR>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. <BR>

+

If this listener is "turned off" remote access to the database is not possible. If this is the case, one's application would fail, resulting in a denial of service.

+

'''Potential areas of attack:'''

'''Potential areas of attack:'''

−

*Stop the Listener - Hence creating a DoS attack.

+

*Stop the Listener - Create a DoS attack.

*Set a password and prevent others from controlling the Listener - Hijack the DB.

*Set a password and prevent others from controlling the Listener - Hijack the DB.

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

+

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

<center>[[Image:Listener_Test.JPG]]</center>

<center>[[Image:Listener_Test.JPG]]</center>

−

<BR>The tool above checks the following:<BR>

+

The tool above checks the following:<br>

'''Listener Password'''

'''Listener Password'''

−

On many Oracle systems the listener password may not be set. The tool above verifies this.

+

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.

+

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'''

'''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.

+

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. Also, detection of brute force attacks on the listener would not be audited.

'''Admin Restrictions'''

'''Admin Restrictions'''

−

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

+

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

−

<br>

+

−

<br>

+

−

'''Example'''<br>

+

'''Example'''

−

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:

+

If you find a TCP/1521 open port on a server, you may have an Oracle Listener that accepts connections from the outside. If the listener is not protected by an authentication mechanism, or if you can find easily a credential, 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:

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

<pre>

<pre>

−

Username Password

+

User name Password

−

OUTLN OUTLN

+

OUTLN OUTLN

−

DBSNMP DBSNMP

+

DBSNMP DBSNMP

−

BACKUP BACKUP

+

BACKUP BACKUP

−

MONITOR MONITOR

+

MONITOR MONITOR

−

PDB CHANGE_ON_INSTALL

+

PDB CHANGE_ON_INSTALL

</pre>

</pre>

−

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:

+

In this case, we have not found privileged DBA accounts, but OUTLN and BACKUP accounts hold a fundamental privilege: EXECUTE ANY PROCEDURE. This means that it is possible to execute all procedures, for example the following:

exec dbms_repcat_admin.grant_admin_any_schema('BACKUP');

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:

+

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

select * from session_privs ;

select * from session_privs ;

Line 74:

Line 73:

<center>[[Image:ToadListener2.PNG]]</center>

<center>[[Image:ToadListener2.PNG]]</center>

−

So the user can now execute a lot of operations, in particular:

+

The user can now execute a lot of operations, in particular:<br>

−

DELETE ANY TABLE

+

DELETE ANY TABLE<br>

−

DROP ANY TABLE.

+

DROP ANY TABLE<br>

+

+

'''Listener default ports'''

+

During the discovery phase of an Oracle server one may discover the following ports. The following is a list of the default ports:

The file ''Listener.ora'' is used to define the database listener properties.

+

One should check that the following line is present in the Listener.ora file:

+

'''ADMIN_RESTRICTIONS_LISTENER=ON'''

+

<br>

+

'''Listener password''':

+

Many common exploits are performed due to the listener password not being set.

+

By checking the Listener.ora file, one can determine if the password is set:

−

{{Category:OWASP Testing Project AoC}}

+

The password can be set manually by editing the Listener.ora file. This is performed by editing the following: PASSWORDS_<listener name>. This issue with this manual method is that the password stored in cleartext, and can be read by anyone with acess to the Listener.ora file.

+

A more secure way is to use the LSNRCTRL tool and invoke the ''change_password'' command.

+

+

LSNRCTL for 32-bit Windows: Version 9.2.0.1.0 - Production on 24-FEB-2004 11:27:55

Brief Summary

The database (DB) listener is a network daemon unique to Oracle databases. It waits for connection requests from remote clients.
This daemon can sometimes be compromised and hence can affect the availability of the database or the validity of data stored within it.

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. The testing outlined in this section is possible if the tester can access this service -- the test should be done from the Intranet (major Oracle installations don't expose this service to the external network).
The listener, by default, listens on port 1521 (port 2483 is the new officially registered port for the TNS Listener and 2484 for the TNS Listener using SSL). It is a good practice to change the listener from this port to another arbitrary port number.
If this listener is "turned off" remote access to the database is not possible. If this is the case, one's application would fail, resulting in a denial of service.

Potential areas of attack:

Stop the Listener - Create a DoS attack.

Set a password and prevent others from controlling the Listener - Hijack the DB.

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:

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. 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 remotely.

Example
If you find a TCP/1521 open port on a server, you may have an Oracle Listener that accepts connections from the outside. If the listener is not protected by an authentication mechanism, or if you can find easily a credential, 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:

In this case, we have not found privileged DBA accounts, but OUTLN and BACKUP accounts hold a fundamental privilege: EXECUTE ANY PROCEDURE. This means that it is possible to execute all procedures, for example the following:

exec dbms_repcat_admin.grant_admin_any_schema('BACKUP');

The execution of this command permits one 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:

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

Listener default ports
During the discovery phase of an Oracle server one may discover the following ports. The following is a list of the default ports:

Gray Box testing and example

Testing for restriction of the privileges of the listener:
It is important to give the listener least privilege so it cannot read or write files in the database or in the server memory address space.

The file Listener.ora is used to define the database listener properties.
One should check that the following line is present in the Listener.ora file:
ADMIN_RESTRICTIONS_LISTENER=ONListener password:
Many common exploits are performed due to the listener password not being set.
By checking the Listener.ora file, one can determine if the password is set:

The password can be set manually by editing the Listener.ora file. This is performed by editing the following: PASSWORDS_<listener name>. This issue with this manual method is that the password stored in cleartext, and can be read by anyone with acess to the Listener.ora file.
A more secure way is to use the LSNRCTRL tool and invoke the change_password command.