Port / TCP
15672RabbitMQ management
The RabbitMQ management plugin's web UI and HTTP API for queues, exchanges, and users.
If it is internet-facing: Finding 15672 open to the internet is a finding in its own right — it warrants an explanation, not just a rule.
Exposure
Behind a gateway
Transport
Cleartext
Risk if public
High
Exposure verdict
Port 15672 should sit behind a reverse proxy, VPN, or source allow-list rather than being forwarded at the perimeter. Publishing it directly puts an administrative or internal interface on the open internet.
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 containers & platform ports so a rule written for one can be checked against its neighbours.
What actually goes wrong
2 notes- The UI can create users and read queued messages, so it is an administrative interface, not a dashboard.
- It is plain HTTP unless a certificate is configured; put it behind a TLS-terminating proxy.
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 15672 proto tcpiptables
sudo iptables -A INPUT -p tcp -s 10.0.0.0/8 --dport 15672 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 15672 -j DROPIf you do need it open to everyone
sudo ufw allow 15672/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 = :15672'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:15672 -sTCP:LISTENmacOS ships lsof rather than ss; this names the owning process and user.
From outside
nmap -sV -Pn -p 15672 <host>A version probe confirms whether RabbitMQ management is actually what answers, rather than trusting the number. Only scan hosts you are authorised to test.
Reachability
nc -vz <host> 15672The quick yes/no when you only need to know whether a path exists through the firewall.