RPC Portmapper Exposed

The RPC portmapper (rpcbind) answers queries from untrusted networks, disclosing the RPC services a host runs and allowing its UDP responses to be abused for reflection attacks.

SeverityMedium
CVSS 3.15.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Open in the calculator
CVSS 4.06.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere
OWASP Top 10A01:2025 Broken Access Control
MITRE ATT&CKT1046 Network Service Discovery, T1498.002 Reflection Amplification
CategoryInformation Disclosure

Description

The RPC portmapper service, rpcbind (historically portmap), can be reached from networks that do not need it. ONC RPC services such as NFS, the NFS mount and lock daemons, NIS and various vendor services register with the portmapper, which tells clients which port each service is using. Any host that can reach TCP or UDP 111 can ask for the full list, including each service's program number, version, transport and port. The list tells an attacker which RPC services the host runs and on which ports, including services that are often weakly protected, such as NFS mount daemons and NIS, which helps them choose further attacks.

Where the portmapper answers on UDP from the internet, an attacker can send it small requests with a forged source address so that it sends larger responses to a victim, contributing to denial-of-service attacks against third parties; CISA's guidance on UDP amplification includes the portmapper among the protocols that can be abused in this way. The portmapper does not itself give access to data or systems, so the impact is limited to this disclosure and to reflection abuse.

The issue is identified with rpcinfo -p or the Nmap rpcinfo script, which return the registered services. Scanners report it as RPC portmapper or rpcbind service detection and, where it answers on UDP from the internet, as a service that can be abused for distributed denial-of-service amplification.

Remediation

Remove the service where it is not needed and restrict it where it is:

  • Disable rpcbind on hosts that do not run RPC services. NFS version 4 does not use it, so servers configured for NFS version 4 only can run without it. On systemd-based Linux systems, stop and disable both the service and its socket unit.
  • Where RPC services are needed, restrict TCP and UDP 111, and the ports the RPC services use, with host and network firewall rules to the clients that use them.
  • Block TCP and UDP 111 at the internet perimeter.
# systemd-based Linux, where no RPC services are needed systemctl disable --now rpcbind.service rpcbind.socket

Confirm the fix by running rpcinfo -p against the host from an untrusted network and checking that no response is received.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Network Services Findings

Every Network Services finding