Port / TCP
1883MQTT
MQTT is a lightweight publish/subscribe broker protocol used across IoT fleets, telemetry, and home automation.
If it is internet-facing: Finding 1883 open to the internet is a finding in its own right — it warrants an explanation, not just a rule.
Exposure
Trusted network only
Transport
Cleartext
Risk if public
High
Exposure verdict
Port 1883 belongs on a trusted internal network. If a perimeter scan finds it answering, treat that as a firewall defect rather than a configuration preference.
Traffic crosses the network readable and modifiable. Anything sensitive on this port needs a tunnel, a VPN, or a different protocol.
Registered with IANA on request, but bindable by any unprivileged user. Registration records intent — it does not reserve the port, so collisions between products are common.
Grouped with the other messaging & media ports so a rule written for one can be checked against its neighbours.
What actually goes wrong
2 notes- Brokers default to allowing anonymous connections, and a subscriber to '#' receives every message on the broker.
- Telemetry topics routinely carry device locations, sensor readings, and control commands.
Recommended firewall rule
Allow only from 10.0.0.0/8, drop the rest
Swap in the CIDR your administrators or application tier actually come from — the point is that the default answer is no.
ufw
sudo ufw allow from 10.0.0.0/8 to any port 1883 proto tcpiptables
sudo iptables -A INPUT -p tcp -s 10.0.0.0/8 --dport 1883 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 1883 -j DROPIf you do need it open to everyone
sudo ufw allow 1883/tcpWrite down why. An unexplained allow rule outlives the person who added it, and the next reviewer has no way to tell a deliberate exception from an accident.
Check what is really there
Listening locally
sudo ss -tlpn 'sport = :1883'The bind address is the answer that matters: 127.0.0.1 is local-only, 0.0.0.0 and :: mean every interface.
Listening (macOS)
sudo lsof -nP -iTCP:1883 -sTCP:LISTENmacOS ships lsof rather than ss; this names the owning process and user.
From outside
nmap -sV -Pn -p 1883 <host>A version probe confirms whether MQTT is actually what answers, rather than trusting the number. Only scan hosts you are authorised to test.
Reachability
nc -vz <host> 1883The quick yes/no when you only need to know whether a path exists through the firewall.
The safer path
port 8883Move to port 8883 — MQTT over TLS
MQTT over TLS does the same job with the session protected from the first byte, so there is no plaintext phase for an on-path attacker to read or strip. Migrating is usually a client configuration change plus a firewall swap.