Port 8080 – HTTP (Alternate / Proxy)

Why It’s Open

Port 8080 is often used when the standard HTTP port (80) is unavailable or when separating dev/staging environments. Also common in web proxies.

Common Risks

• Admin Interfaces Exposed: Dashboards and web consoles on dev ports.
• Directory Traversal & File Disclosure: In apps running without hardening.
• Proxy Abuse: If misconfigured, it can relay arbitrary web traffic.

Want to save time on reporting?

Let PentestPad generate, track, and export your reports - automatically.

Book a Demo

Enumeration & Testing

Nmap

nmap -p 8080 -sV

nmap -p 8080 --script http-title,http-methods
curl http://:8080

What to Look For

Known Exploits

1. CVE-2017-12149 In JBoss Application Server as shipped with Red Hat Enterprise Application Platform 5.2, the doFilter method in the ReadOnlyAccessFilter of the HTTP Invoker does not restrict classes for which it performs deserialization, allowing an attacker to execute arbitrary code via crafted serialized data. 🔗 NVD Entry

Mitigation

• Require authentication for all admin interfaces.
• Use HTTPS even on alternate ports.
• Limit access to internal networks.
• Harden web servers and sanitize inputs.

Real-World Example

Misconfigured admin panels running on port 8080 have been responsible for major data breaches, especially in exposed cloud environments.

TL;DR

• Service: HTTP Alternate (Web Services)
• Default Port: 8080
• Risks: Deserialization vulnerabilities leading to RCE
• Mitigation: Update application servers, restrict access