Common attacks and weaknesses
- Log injection if client certificates are not checked.
Encrypted syslog transport.
The monitoring server collects metrics, alerts or logs from devices over port 6514. Everything is encrypted: someone on the path only sees unreadable bytes.
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| syslog-tls | 6514 | TCP, UDP, DCCP | Syslog over TLS | RFC 5425 | - |
// source: IANA service name and port number registry
Linux
sudo ss -ltnup 'sport = :6514' # process listening on 6514
sudo lsof -nP -i :6514macOS
sudo lsof -nP -i :6514
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 6514 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 6514 netstat -ano | findstr :6514
From another machine
nmap -p 6514 -sV <host> sudo nmap -sU -p 6514 <host> nc -zv <host> 6514
Block it in the firewall
sudo ufw deny 6514/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 6514" -Direction Inbound -LocalPort 6514 -Protocol TCP -Action Block # Windows
Encrypted syslog transport.
Port 6514 is registered for TCP and UDP and DCCP. In practice the service mostly uses TCP.
It is rated 2/10 (low) when exposed to the Internet. Log injection if client certificates are not checked. Use mutual TLS between log sources and collectors.
On Linux run "ss -ltnup 'sport = :6514'", on macOS "lsof -nP -i :6514", and on Windows "netstat -ano | findstr :6514" to see the local process. From another machine, "nmap -p 6514 <host>" shows whether it is reachable.