Common attacks and weaknesses
- Rogue DHCP servers redirecting traffic (man in the middle).
- DHCP starvation.
DHCP server side (clients use 68).
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 |
|---|---|---|---|---|---|
| bootps | 67 | TCP, UDP | Bootstrap Protocol Server | RFC 951 | - |
// source: IANA service name and port number registry
Linux
sudo ss -ltnup 'sport = :67' # process listening on 67
sudo lsof -nP -i :67macOS
sudo lsof -nP -i :67
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 67 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 67 netstat -ano | findstr :67
From another machine
nmap -p 67 -sV <host> sudo nmap -sU -p 67 <host> nc -zv <host> 67
Block it in the firewall
sudo ufw deny 67/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 67" -Direction Inbound -LocalPort 67 -Protocol TCP -Action Block # Windows
DHCP server side (clients use 68).
Port 67 is registered for UDP and TCP. In practice the service mostly uses UDP.
It is rated 4/10 (moderate) when exposed to the Internet. Rogue DHCP servers redirecting traffic (man in the middle). Enable DHCP snooping on switches.
On Linux run "ss -ltnup 'sport = :67'", on macOS "lsof -nP -i :67", and on Windows "netstat -ano | findstr :67" to see the local process. From another machine, "nmap -p 67 <host>" shows whether it is reachable.