Irked_RPC

RPC

---

Nmap discovered a RPC service on the target port 111

┌──(kali㉿kali)-[~/archive/htb/labs/irked]
└─$ rpcinfo $IP  
   program version netid     address                service    owner
    100000    4    tcp6      ::.0.111               portmapper superuser
    100000    3    tcp6      ::.0.111               portmapper superuser
    100000    4    udp6      ::.0.111               portmapper superuser
    100000    3    udp6      ::.0.111               portmapper superuser
    100000    4    tcp       0.0.0.0.0.111          portmapper superuser
    100000    3    tcp       0.0.0.0.0.111          portmapper superuser
    100000    2    tcp       0.0.0.0.0.111          portmapper superuser
    100000    4    udp       0.0.0.0.0.111          portmapper superuser
    100000    3    udp       0.0.0.0.0.111          portmapper superuser
    100000    2    udp       0.0.0.0.0.111          portmapper superuser
    100000    4    local     /run/rpcbind.sock      portmapper superuser
    100000    3    local     /run/rpcbind.sock      portmapper superuser
    100024    1    udp       0.0.0.0.216.228        status     107
    100024    1    tcp       0.0.0.0.137.150        status     107
    100024    1    udp6      ::.151.166             status     107
    100024    1    tcp6      ::.188.206             status     107

The RPC service has only the portmapper bound to it. That alone doesn’t get me anywhere, and it also doesn’t seem to provide any additional context