Common attacks and weaknesses
- Responder-style poisoning captures NTLM hashes on internal networks.
Windows name resolution fallback on the local network.
A device asks the whole local network a question and the device that matches answers. It travels in clear text: anyone on the path can read it.
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| llmnr | 5355 | TCP, UDP | LLMNR | - | 2004-06 |
// source: IANA service name and port number registry
Linux
sudo ss -ltnup 'sport = :5355' # process listening on 5355
sudo lsof -nP -i :5355macOS
sudo lsof -nP -i :5355
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 5355 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 5355 netstat -ano | findstr :5355
From another machine
nmap -p 5355 -sV <host> sudo nmap -sU -p 5355 <host> nc -zv <host> 5355
Block it in the firewall
sudo ufw deny 5355/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 5355" -Direction Inbound -LocalPort 5355 -Protocol TCP -Action Block # Windows
Windows name resolution fallback on the local network.
Port 5355 is registered for UDP and TCP. In practice the service mostly uses UDP.
It is rated 6/10 (high) when exposed to the Internet. Responder-style poisoning captures NTLM hashes on internal networks. Disable LLMNR and NetBIOS name resolution by Group Policy.
On Linux run "ss -ltnup 'sport = :5355'", on macOS "lsof -nP -i :5355", and on Windows "netstat -ano | findstr :5355" to see the local process. From another machine, "nmap -p 5355 <host>" shows whether it is reachable.