Report this

What is the reason for this report?

Port 2052 is open even without firewall rule

Posted on June 8, 2021

A recently conducted security scan highlighted that several ports were open and therefore presented a security vulnerability: 2052 2053 2082 2083 2086 2087 …

I ran sudo nmap -sS -Pn -p 2052 -T4 -vv --reason xxx.xxx.xxx.xxx and found that 2052 was open.

Why is port 2052 (and presumably the other ports listed) open even though they should presumably be blocked by the firewall?



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

This comment has been deleted

Hi there,

Looking at the ports it seems like a cPanel/WHM server. Are you using CSF as the firewall?

If so you need to explicitly close the ports via CSF by removing them from the Allowed hosts list in the /etc/csf/csf.conf file and then restarting CSF with this command:

csf -r

Also if the ports are already closed, any IP addresses that have been allowed via CSF would have access to all ports even though the ports are closed. So you need to remove the IP address of the penetration testing company from the CSF allow list in order to have valid results.

Regards, Bobby

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.