Port / TCP
8080HTTP alternate
The conventional unprivileged HTTP port for application servers, admin consoles, and containers behind a reverse proxy.
If it is internet-facing: Port 8080 is legitimate in the right place, but exposed carelessly it widens the attack surface noticeably.
Exposure
Behind a gateway
Transport
Cleartext
Risk if public
Elevated
Exposure verdict
Port 8080 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 web & proxies ports so a rule written for one can be checked against its neighbours.
What actually goes wrong
2 notes- Traffic between the proxy and the app is plaintext, which matters when they are not on the same host.
- Admin consoles that land here (Tomcat manager, Jenkins) are frequently found with default credentials.
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 8080 proto tcpiptables
sudo iptables -A INPUT -p tcp -s 10.0.0.0/8 --dport 8080 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 8080 -j DROPIf you do need it open to everyone
sudo ufw allow 8080/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 = :8080'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:8080 -sTCP:LISTENmacOS ships lsof rather than ss; this names the owning process and user.
From outside
nmap -sV -Pn -p 8080 <host>A version probe confirms whether HTTP alternate is actually what answers, rather than trusting the number. Only scan hosts you are authorised to test.
Reachability
nc -vz <host> 8080The quick yes/no when you only need to know whether a path exists through the firewall.
The safer path
port 8443Move to port 8443 — HTTPS alternate
HTTPS alternate 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.