Skip to content

RPCBind / Portmapper:

Vulnerability Discovery

Find dangerous RPC services via portmapper like NFS, NIS, rexd

1 guide • Created Mar 30, 2026 • Updated Mar 30, 2026
1 guide

RPCBind vulnerability discovery centers on information disclosure and the services it exposes. The portmapper itself leaks the full list of registered RPC programs, versions, and their listening ports, giving attackers a map of high-port services that would otherwise require exhaustive scanning to find.

Exposed RPCBind on the internet or across trust boundaries is a finding on its own: it reveals internal service architecture and directs targeted attacks against NFS, NIS, mountd, and other registered programs. Check whether RPCBind is filtered or accessible from untrusted networks using Nmap against port 111 (TCP and UDP).

Older rpcbind and portmapper implementations have known vulnerabilities including denial of service and memory corruption bugs. Cross-reference the target OS and rpcbind version against CVE databases. The real risk, though, is usually not in portmapper itself but in the services it advertises, treat the program listing as your attack surface map.