Skip to main content

Overview

impacket-rpcdump queries the RPC Endpoint Mapper (port 135) to enumerate all registered RPC interfaces and endpoints on a target. The output reveals which services are running and listening, which is valuable for attack planning. Works with NULL sessions by default since the RPC Endpoint Mapper is typically accessible without authentication.

Basic Usage

Dump all RPC endpoints:
With explicit port:
Output includes protocol, endpoint, UUID, and interface name:

Interesting Interfaces

MS-RPRN (PrinterBug / SpoolService)

UUID: 12345678-1234-ABCD-EF00-0123456789AB If the Print Spooler service is running, the target is vulnerable to the PrinterBug (coerce authentication back to attacker).
Exploit with:

MS-EFSRPC (PetitPotam)

UUID: c681d488-d850-11d0-8c52-00c04fd90f7e (lsarpc) UUID: df1941c5-fe89-4e79-bf10-463657acf44d (efsrpc) Encrypting File System Remote Protocol. Allows unauthenticated coercion on unpatched DCs.
Exploit with:

MS-DFSNM (DFSCoerce)

UUID: 4fc742e0-4a10-11cf-8273-00aa004ae673 Distributed File System Namespace Management. Another coercion vector.
Exploit with:

Other Notable Interfaces


Filter by Specific Port

Show only endpoints bound to a specific port:
Show only named pipe bindings:
Show only TCP bindings:

Authentication

Most of the time, rpcdump works without credentials (NULL session):
With credentials (if NULL session is blocked):
Pass-the-hash:

Using Output for Attack Planning

Run rpcdump and check which attack paths are available:
Typical workflow:
  1. Run rpcdump on the DC
  2. Identify exposed coercion interfaces (RPRN, EFSRPC, DFSNM)
  3. Set up ntlmrelayx or Responder
  4. Trigger coercion to capture or relay the DC machine account hash

rpcclient (from Samba) complements rpcdump for deeper interaction:

Quick Reference