Working with Solaris RPC Services

News	Summary	OSI Protocol Layers	Recommended Books	Recommended Links	Lecture Notes	Unix System Calls
Security Issues		MSBlaster Worm	Microsoft RPC		Humor	Etc

Lecture Notes

Introduction
Starting RPC Services at Boot Time
Starting RPC Services on Demand
Using the rpcinfo Command
- Registration of RPC services
- Deleting RPC Service Registration

Summary

There are two ways of starting RPC services: at boot time via RC files or on demand.

At boot time RPC services vai /etc/rc2.d/s71rpc startup script that initializes the rpcbind service After the system starts up, the rpcbind daemon starts listening at port 111. The rpcbind process associates RPC program numbers with port numbers above 32768. The port number used by the rpcbind daemon is listed in the /etc/inet/services file. To view the port number and protocol, perform the command:

grep rpcbind /etc/services

sunrpc 111/udp rpcbind
sunrpc 111/tcp rpcbind

For a client to make request to the server the rpcbind service must be running on the server system. When an RPC service starts at boot, it communicates port and RPC number to the rpcbind process: If the RPC service has registered its current port number with the rpcbind daemon during startup, the current port number of the RPC service is returned to the client.

Some rpcbind services start only on demand. They are listed in inetd.conf file and are controlled by inetd daemon.

The rpcinfo command is used to list and delete RPC services. Two corresponding options are -p and -d:

-p host command returns information about registered RPC services on the specified host.
-d prognum versnum To unregister the RPC service given a specified prognum (program number) and versnum (version number):
- rpcinfo -d prognum versnum
  For example:
  # rpcinfo -d 100012 1
You can also check the /etc/rpc file to see if the particular service service is listed.

# grep sprayd /etc/rpc

sprayd 100012 spray

Introduction

Sun Microsystems's invented RPC in mid 80th. The original version of RPC was defined in RFC 1050. RPC is a powerful technique for constructing distributed, client-server based applications. It is based on extending the notion of conventional, or local procedure calling, so that the called procedure need not exist in the same address space as the calling procedure.

RPC opened new possibilities in network programming making possible such protocols as NFS, NIS, rsh, etc. Network File System (NFS) is a network file sharing system application that is a good example of how RPC can be used. Version 2 of RPC is defined in RFC 1057 and RFC 1831.

RPC services are not typically assigned to well-known ports. Rather than tying applications to particular ports, RPC provides a port mapping service whereby RPC assigns port numbers above 1024 to applications that are written to request RPC for ports. The lookup services that can be used for this include PORTMAPPER (PMAP) and RPCBIND and are described in RFC 1833. Portmapper has a fixed port (either UDP or TCP) number 111 to which an application (RPC service) makes a call to gain a port number to use. This lookup service program must be started first and remain operational throughout the runtime of the application.

The list of RPC services includes:

Services that start by default at system boot time
Services that do not start automatically at boot and must be started manually or on demand

While originated in Sun RPC spread first to other Unixes and then to other OSes like Windows becoming pretty much a cross-platform protocol. Even command line utilities are often replicated. For example, Windows has rpcinfo utilities that operates pretty much like its Unix counterpart. To ensure cross-platform compatibility RPC data now are encoded using eXternal Data Representation (XDR), which defines how integers, floating point numbers and strings are represented(RFC 1832). This Presentation Layer protocol enables different computers with different operating systems to interact seamlessly. There is no formal message header or protocol system for XDR. XDR uses an 8-bit byte, with the lower bytes being the most significant. The RFC defines that all integer data types are converted to 4-byte integers, (there is also available an extended 64-bit integer format). IEEE 32-bit formats are used for floating-point numbers, where the mantissa is the lower 23 bits, the exponent takes 8 bits, and the sign of the number is 1 bit. Where data takes less than 4 bytes for any type, padding is added to ensure 4-byte lengths

Starting RPC Services at Boot Time

RPC services started at boot time with startup scripts run on available ports above 32768. The rpcbind process associates RPC program numbers with port numbers.

The rpcbind service must be running on the server system for you to make RPC requests to the server. When an RPC service starts at boot, it communicates the following information to the rpcbind process:

The port with which it is associated
The RPC program number

If a client wants to make an RPC call to a given program number, it must first contact the rpcbind service on the server machine to obtain the port address before it can send the RPC requests. If the RPC service has registered its current port number with the rpcbind daemon during startup, the current port number of the RPC service is returned to the
client.

In Solaris the /etc/rc2.d/s71rpc startup script initializes the rpcbind service. The port number used by the rpcbind daemon is listed in the /etc/inet/services file. After the system starts up, the rpcbind daemon starts listening at port 111. To view the port number and protocol, grep the /etc/inet/services for string "rpcbind":

# grep rpcbind /etc/services

sunrpc 111/udp rpcbind
sunrpc 111/tcp rpcbind

Starting RPC Services on Demand

Some rpcbind services start only on demand. The port numbers are registered with the rpcbind process during boot. When a client application requests a service, the rpcbind process returns the port number of the service to the client machine. The client machine generates a new request using the port number that it just received for the requested service.

RPC services on demand, such as the sprayd service, are implemented as follows:

The rpcbind daemon is started on all systems by a startup script. The sprayd service is listed in both the /etc/rpc and /etc/inetd.conf files and, therefore, registers its current port assignment and program number with the rpcbind process during boot.
A user on host alpha issues a spray command to host beta. The spray request is initially addressed to port 111 and contains the program number of the sprayd service.
The rpcbind daemon on the host beta (server) reads the program number and determines that the request is for the sprayd service. The rpcbind daemon returns the current port number of the sprayd service to the host alpha ( client).
The host alpha (client) sends a second request to the port number of the sprayd service on the host beta (server). The inetd daemon receives the request.
The inetd daemon consults entries in the /etc/inetd.conf file to find a matching entry for the service request. The inetd daemon starts the sprayd service.
This rpc.sprayd daemon takes over the spray session’s communication.

Using the rpcinfo Command

The rpcinfo command makes an RPC call to an RPC server, and reports what it finds. Two frequently used options to the rpcinfo command are -p and -d.

Registration of RPC services. RPC services need to be registered. You can list services and unregister any services with rpcinfo. Note – Using the command rpcinfo -p host command returns information about registered RPC services on the specified host.

Listing Registered RPC Services To list all the services registered with the rpcbind process, enter the
rpcinfo command as follows:
rpcinfo -p [ host ]
For example:
# rpcinfo -p
program    vers proto port    service
100000     4     tcp    111    rpcbind
100000     3     tcp    111    rpcbind
100000     2     tcp    111    rpcbind
100000     4     udp    111    rpcbind
100000     3     udp    111    rpcbind
100000     2     udp    111    rpcbind
100232    10     udp    32772 sadmind
100083     1     tcp    32771
...
<output truncated>
...

The columns are as follows:
- Program number
- Version number of the RPC program number
- RPC protocol
- Port number
- RPC service
Deleting RPC Service Registration
To unregister the RPC service given a specified prognum (program number) and versnum (version number), perform the rpcinfo command:
- rpcinfo -d prognum versnum
  For example:
  # rpcinfo -d 100012 1
This command unregisters the RPC service with program number 100012 and version number 1.

Note – When using the rpcinfo -d command to unregister an RPC service, the RPC service can be identified using either the service name or the program number.

The deleted RPC service that uses program number 100012 is sprayd. To register the sprayd service again, send a HUP signal to the inetd daemon as follows:

# pkill -HUP inetd

Notes:

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Some amount of grammar and spelling errors should be expected.
The site contain some broken links as it develops like a living tree... Please try to use Google, Open directory, etc. to find a replacement link (see HOWTO search the WEB for details). We would appreciate if you can mail us a correct link.

Google Search
Open directory	Research Index

Security Issues

See also MSBlaster Worm -- the most high profile exploitation of RPC vulnerabilities in MS Windows.

DRAFT - Sun Remote Procedure Call

There are several problems with RPC itself, some more security related than others. The portmapper itself can be persuaded to "forward" requests to services which may then be fooled into thinking that they come from the local machine. The standard portmappers provide very little in the way of access control or logging. Wietse Venema has a version of the portmapper which does provide these extra services. [Solaris 10 implements this wrapper -NNB].

The more common problems are with the RPC services themselves. They are typically appallingly badly written from the security perspective and are a common source of network weaknesses..,

RPC Interface Buffer Overflow (7.17.03)

Microsoft has published an advisory regarding buffer overflow vulnerability present in the windows RPC Service. The RPC service provides remote procedure calls between objects executing on two remote machines running the Windows operating system.

SCOPE

An attacker can exploit this vulnerability by crafting a specifically malformed RPC packet and sending it to a vulnerable server. The attacker will need access to the vulnerable server RPC interface that is located at port 135.

A malicious attacker may use this vulnerability to execute code of his choice on the victim machine. Since the RPC service executes with SYSTEM privileges an attacker executing code as the result of this attack can fully compromise the vulnerable server

VERSIONS AFFECTED
Windows NT 4.0 - All service packs
Windows 2000 - All service packs
Apply the MS03-039 patch (includes MS03-026 patch) Please refer to:

Microsoft Security Bulletin MS03-026 for more information: http://www.microsoft.com/technet/treeview/default.asp? url=/technet/security/bulletin/MS03-026.asp

Microsoft Security Bulletin MS03-039 for more information: http://www.microsoft.com/technet/treeview/default.asp? url=/technet/security/bulletin/MS03-039.asp

2. Block port 135 when RPC service is not required