Common attacks and weaknesses
- Brokers without authentication exposing sensor data and accepting commands.
IoT messaging protocol (8883 for MQTT over TLS).
Producers publish messages into a queue on port 1883; consumers pick them up in order, at their own pace. It travels in clear text: anyone on the path can read it.
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| mqtt | 1883 | TCP, UDP | Message Queuing Telemetry Transport Protocol | - | 2015-02-10 |
// source: IANA service name and port number registry
Linux
sudo ss -ltnup 'sport = :1883' # process listening on 1883
sudo lsof -nP -i :1883macOS
sudo lsof -nP -i :1883
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 1883 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 1883 netstat -ano | findstr :1883
From another machine
nmap -p 1883 -sV <host> sudo nmap -sU -p 1883 <host> nc -zv <host> 1883
Block it in the firewall
sudo ufw deny 1883/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 1883" -Direction Inbound -LocalPort 1883 -Protocol TCP -Action Block # Windows
IoT messaging protocol (8883 for MQTT over TLS).
Port 1883 is registered for TCP and UDP. In practice the service mostly uses TCP.
It is rated 7/10 (high) when exposed to the Internet. Brokers without authentication exposing sensor data and accepting commands. Require authentication and TLS (8883); restrict topic ACLs.
On Linux run "ss -ltnup 'sport = :1883'", on macOS "lsof -nP -i :1883", and on Windows "netstat -ano | findstr :1883" to see the local process. From another machine, "nmap -p 1883 <host>" shows whether it is reachable.