Real-time collaboration for Jupyter Notebooks, Linux Terminals, LaTeX, VS Code, R IDE, and more,
all in one place.
Real-time collaboration for Jupyter Notebooks, Linux Terminals, LaTeX, VS Code, R IDE, and more,
all in one place.
Path: blob/master/documentation/modules/auxiliary/scanner/misc/sunrpc_portmapper.md
Views: 11784
Vulnerable Application
RPC Portmapper, or more recently renamed to rpcbind, is fairly common and this scanner searches for its existence. The idea behind rpcbind was to create a 'directory' that could be asked where a service is running (port). Having this single port/service be queryable meant, the services being managed by rpcbind could actually be running on any port or protocol, and rpdbind would be in charge of letting clients know where they were. This is more or less an outdated model/service, and NFS is arguably the most popular service still utilizing rpcbind. The following was done on Kali linux:
Install rpcbind:
apt-get install rpcbind
Now now have
rpcbind
, but this gives us minimal services running on it. You may want to install additional: * NIS:apt-get install nis
Start the service:
ypserv
Just to be safe, restart rpcbind:
service rpcbind restart
Verification Steps
Install and configure rpcbind
Start msfconsole
Do:
use auxiliary/scanner/misc/sunrpc_portmapper
Do:
run
Scenarios
A run against the configuration from these docs
Confirming
Since rpc port mapper has been around since 1995, there are many tools which can also query it. The following are other industry tools which can also be used.
nmap
rpcinfo
This is the standard package included with rpcbind to query the rpc interface.