Common attacks and weaknesses
- Remote enumeration of RPC services.
- Lateral movement with WMI and DCOM.
- Historic worms (Blaster, MS03-026).
Microsoft RPC endpoint mapper, used by DCOM, WMI and many Windows services.
The client sends a request to port 135 and the MS RPC service answers. It travels in clear text: anyone on the path can read it.
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| epmap | 135 | TCP, UDP | DCE endpoint resolution | - | - |
// source: IANA service name and port number registry
Linux
sudo ss -ltnup 'sport = :135' # process listening on 135
sudo lsof -nP -i :135macOS
sudo lsof -nP -i :135
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 135 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 135 netstat -ano | findstr :135
From another machine
nmap -p 135 -sV <host> sudo nmap -sU -p 135 <host> nc -zv <host> 135
Block it in the firewall
sudo ufw deny 135/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 135" -Direction Inbound -LocalPort 135 -Protocol TCP -Action Block # Windows
Microsoft RPC endpoint mapper, used by DCOM, WMI and many Windows services.
Port 135 is registered for TCP and UDP. In practice the service mostly uses TCP.
It is rated 8/10 (high) when exposed to the Internet. Remote enumeration of RPC services. Block at the edge.
On Linux run "ss -ltnup 'sport = :135'", on macOS "lsof -nP -i :135", and on Windows "netstat -ano | findstr :135" to see the local process. From another machine, "nmap -p 135 <host>" shows whether it is reachable.