Port / TCP
2375Docker API (plaintext)
The Docker daemon's remote API without TLS or authentication of any kind.
If it is internet-facing: Finding 2375 open to the internet is a finding in its own right — it warrants an explanation, not just a rule.
Exposure
Localhost only
Transport
Cleartext
Risk if public
High
Exposure verdict
Port 2375 should be bound to 127.0.0.1. Nothing outside the host needs to reach it, and binding to 0.0.0.0 is the single change that turns it into an incident.
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- Anyone who reaches this port can start a privileged container that mounts the host filesystem — it is root on the host.
- Exposed Docker sockets are scanned for continuously and used to deploy cryptominers within minutes.
Recommended firewall rule
Deny at the edge and bind to loopback
A firewall rule is the second line here. Fix the bind address in the service configuration so the listener never leaves the host.
ufw
sudo ufw deny 2375/tcpiptables
sudo iptables -A INPUT -p tcp --dport 2375 -j DROPIf you do need it open to everyone
sudo ufw allow 2375/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 = :2375'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:2375 -sTCP:LISTENmacOS ships lsof rather than ss; this names the owning process and user.
From outside
nmap -sV -Pn -p 2375 <host>A version probe confirms whether Docker API (plaintext) is actually what answers, rather than trusting the number. Only scan hosts you are authorised to test.
Reachability
nc -vz <host> 2375The quick yes/no when you only need to know whether a path exists through the firewall.
The safer path
port 2376Move to port 2376 — Docker API (TLS)
Docker API (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.