Note: This is an archival copy of Security Sun Alert 228554 as previously published on http://sunsolve.sun.com.|
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1017448.1.
Solaris 9 Operating System
Solaris 2.6 Operating System
Solaris 7 Operating System
Solaris 8 Operating System
Date of Resolved Release
rpcbind(1M) may be terminated by a local or remote unprivileged user. This would cause a denial of service to RPC applications hosted on the affected system.
This issue can occur in the following releases:
Solaris 2.5.1 will not be evaluated regarding the potential impact of the issue described in this Sun Alert document.
Note: Patch 108827-40 has been obsoleted by patch 108993-18. Patch 108828-40 has been obsoleted by patch 108994-18.
The "rpcbind" process is no longer running.
When executed, the rpcinfo(1M) command will display an error message as in the following example:
$ rpcinfo rpcinfo: can't contact rpcbind: RPC: Rpcbind failure - RPC: Failed (unspecified error)
As a precaution, consider refusing access to rpcbind(1M) from untrusted networks. This can be achieved by blocking connections from untrusted networks to ports used by rpcbind(1M) (typically ports 111/UDP and 111/TCP; use "rpcinfo | grep rpcbind" to determine UDP/TCP ports in use by rpcbind(1M))
To facilitate restarting rpcbind(1M), consider generating a list of currently registered RPC services. This can be done by once terminating the "rpcbind" process with a "TERM" signal after all hosted RPC services have been started and restarting it with the "-w " option:
# pkill -TERM rpcbind # /usr/sbin/rpcbind -w
As a result, the "rpcbind" process will write a list of all currently registered RPC services to the "/tmp/rpcbind.file" and /"tmp/portmap.file" files.
Should the "rpcbind" process exit unexpectedly later it can be restarted with the "-w" option to re-register RPC services available at the time the "pkill -TERM rpcbind" was issued:
# /usr/sbin/rpcbind -w
This will eliminate the need to restart hosted RPC services after restarting rpcbind(1M).
This issue is addressed in the following releases:
This solution has no attachment