Common attacks and weaknesses
- Session hijacking or resets; route leaks.
Border Gateway Protocol between routers.
The client sends a request to port 179 and the BGP service answers. It travels in clear text: anyone on the path can read it.
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| bgp | 179 | TCP, UDP, SCTP | Border Gateway Protocol | - | - |
// source: IANA service name and port number registry
Linux
sudo ss -ltnup 'sport = :179' # process listening on 179
sudo lsof -nP -i :179macOS
sudo lsof -nP -i :179
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 179 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 179 netstat -ano | findstr :179
From another machine
nmap -p 179 -sV <host> sudo nmap -sU -p 179 <host> nc -zv <host> 179
Block it in the firewall
sudo ufw deny 179/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 179" -Direction Inbound -LocalPort 179 -Protocol TCP -Action Block # Windows
Border Gateway Protocol between routers.
Port 179 is registered for TCP and UDP and SCTP. In practice the service mostly uses TCP.
It is rated 6/10 (high) when exposed to the Internet. Session hijacking or resets; route leaks. Allow only configured peers, use TCP-AO or MD5 and RPKI validation.
On Linux run "ss -ltnup 'sport = :179'", on macOS "lsof -nP -i :179", and on Windows "netstat -ano | findstr :179" to see the local process. From another machine, "nmap -p 179 <host>" shows whether it is reachable.