0

I am running a web application on Tomcat (port 8080) with Apache (port 80) in front (on Ubuntu) using mod-proxy_http as the connector. The app is available through port 80 but also through port 8080. This is actually quite useful (when deploying/testing).

Are there are any particular disadvantages/vulnerabilities with keeping port 8080 open in this way?

1 Answer 1

2

My opinion is that you should close 8080 port, or at least allow it for certain host/IP. Less open ports, less problems. Opening port 8080 could let attacker to have more entry points (80 and 8080, using different technologies) and exploit different techniques. Also HTTPd server has much better security modules.

Have you consider using mod_ajp_proxy?

Hope this helps.

Sign up to request clarification or add additional context in comments.

2 Comments

I looked at mod_ajp_proxy but found the http easier to understand and set up (my first time setting up this type of thing). But really I'd like to keep the http because it allows sanity testing of a new deployment of app (while a maintenance page is being served through port 80). I find this very useful.
I think that you can achieve same easy of development/testing if you allow access to port 8080 only for specific IPs. It's much better from security point of view.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.