What does this setting do? Admin_Restrictions_listenerName=ON

Posted on 2008-06-23
Last Modified: 2013-12-18

        What does the following setting do specifically?

The setting is supposed to be set in the listener.ora file. Where in the file would you set this?

Thank You, Missy Madi
Question by:missymadi
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
LVL 74

Expert Comment

ID: 21847338
you can put that anywhere in the listener file.

So, if your listener is called "LISTENER"  then

admin_restrictions_listener = ON

will turn it on

From the 10g Net Services Reference....

Use the parameter ADMIN_RESTRICTIONS_listener_name to restrict runtime
administration of the listener. The parameter is useful if the listener is not

Setting ADMIN_RESTRICTIONS_listener_name=on disables the runtime
modification of parameters in listener.ora. That is, the listener will refuse to
accept SET commands that alter its parameters. To change any of the parameters in
listener.ora, including ADMIN_RESTRICTIONS_listener_name itself, modify
the listener.ora file manually and reload its parameters (with the RELOAD
command) for the new changes to take effect without explicitly stopping and
restarting the listener.

Oracle Corporation recommends establishing a password to secure the listener. To
establish an encrypted password, use either the Listener Control utility CHANGE_PASSWORD command or Oracle Net Manager.

LVL 48

Accepted Solution

schwertner earned 50 total points
ID: 21847425


> DESCRIPTION: The ADMIN_RESTRICTIONS flag has not been set.

> VERSION: Oracle8i and later

> CVE REFERENCE: CVE-2000-0818

> SUMMARY: If a password is not set on the listener service, an attack can read and write files on the operating system. To alleviate this issue, Oracle added a new parameter called ADMIN_RESTRICTIONS. The ADMIN_RESTRICTIONS flag disables the ability of the listener controller to set parameters, thereby not allowing remote users to set parameters. After setting this parameter, you must edit the listener parameters directly in the listener.ora file.

> OVERVIEW: If the listener password has not been set properly, an attacker can set any of the listener parameters. With this ability, an attacker could change the location or name of the trace or log file to create new files or append data to existing files. Once the log or trace file is changed, packets can be generated and sent to the listener which in turn will write them to the trace and log files.

This attack can be mounted by any remote users that can send packets to the IP address and port of the listener. It can not be mounted by an attacker outside your organization if a firewall is properly protecting the database.

This type of attack results in the following possible issues:

- corrupting files such as the database files

- creating files such as .rhost files allowing access directly to the operating system

For instance, a packet with a connect string formatted as below would write a `+ +` on a single line, enough to allow an attacker to rlogin to the operating system.


+ +

To alleviate this issue, Oracle released a patch which added a flag to the listener.ora file. The new parameter, ADMIN_RESTRICTIONS_[listener_name], can be set in the listener.ora, the control file for the Oracle listener program. Replace the [listener_name] within the parameter name with the listener name for the specific listener the patch is being applied to. Setting ADMIN_RESTRICTIONS_[listener_name]=ON stops an attack by not allowing run-time modification of parameters in listener.ora. After setting this parameter, the listener program will refuse to accept SET commands that alter its parameters and attempting to issue a SET command will result in the generation of an error message. Thus, to change any one of the parameters in listener.ora, including ADMIN_RESTRICTIONS_[listener_name] itself, this file needs to be edited directly and the parameters need to be reloaded (e.g., LSNRCTL RELOAD) for the new changes to take effect. You can also stop and restart the listener program to reload these parameters. Operating system access to the protected Oracle account owner directories and files is required to edit listener.ora. Note that the Oracle account owner directories and files must be protected on the operating system by setting the access control permissions on them as recommended by Oracle Corporation in its user manuals.

ADMIN_RESTRICTIONS_[listener_name]=OFF is the default value when the listener program is installed in order to maintain current customer environments and backward compatibility. There is no change in the run-time behavior of the listener program or in the syntax of the SET commands in this mode of operation. You should set the listener password even if you have set this parameter.

> FIX/RECOMMENDATION: To set the parameter, add or modify the ADMIN_RESTRICTIONS_[listener name] parameter to the listener.ora file. Add the line ADMIN_RESTRICTIONS_[listener name] = ON (where [listener name] is the actual listener name in the listener.ora file) .  

Then use the lsnrctl process to stop and start the Oracle listener or to reload the parameters.  This will stop any value from being dynamically set.

LVL 74

Expert Comment

ID: 21857067
schwertner, wouldn't you say a split is in order here?

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
SYS password changed. Now can't log in as SYS 27 60
running myfile.SQL from command line SQLPLUS 12c does not exit. 7 50
error doing substr 3 51
Oracle performance tuning 2 52
Truncate is a DDL Command where as Delete is a DML Command. Both will delete data from table, but what is the difference between these below statements truncate table <table_name> ?? delete from <table_name> ?? The first command cannot be …
How to Create User-Defined Aggregates in Oracle Before we begin creating these things, what are user-defined aggregates?  They are a feature introduced in Oracle 9i that allows a developer to create his or her own functions like "SUM", "AVG", and…
Via a live example show how to connect to RMAN, make basic configuration settings changes and then take a backup of a demo database
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question