Port / TCP
5672AMQP / RabbitMQ
The AMQP 0-9-1 broker port used by RabbitMQ and other message queues for publishing and consuming.
If it is internet-facing: Finding 5672 open to the internet is a finding in its own right — it warrants an explanation, not just a rule.
Exposure
Trusted network only
Transport
Encryption optional
Risk if public
High
Exposure verdict
Port 5672 belongs on a trusted internal network. If a perimeter scan finds it answering, treat that as a firewall defect rather than a configuration preference.
Encryption is available but negotiated or configured rather than guaranteed. A client that does not insist on it will silently fall back to plaintext.
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- The default guest/guest account is restricted to localhost — a broker reachable elsewhere needs real users and vhost permissions.
- Queue contents are application payloads: orders, tokens, personal data.
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 5672 proto tcpiptables
sudo iptables -A INPUT -p tcp -s 10.0.0.0/8 --dport 5672 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 5672 -j DROPIf you do need it open to everyone
sudo ufw allow 5672/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 = :5672'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:5672 -sTCP:LISTENmacOS ships lsof rather than ss; this names the owning process and user.
From outside
nmap -sV -Pn -p 5672 <host>A version probe confirms whether AMQP / RabbitMQ is actually what answers, rather than trusting the number. Only scan hosts you are authorised to test.
Reachability
nc -vz <host> 5672The quick yes/no when you only need to know whether a path exists through the firewall.
The safer path
no port changeChange the configuration, not the port
AMQPS on 5671 wraps the same protocol in TLS.
The fix here lives in the service configuration rather than in a different port assignment.