Unnecessary Network Services Exposed
Hosts expose network services that serve no business purpose, adding to the attack surface available to an attacker without any benefit to the organisation.
| Severity | Low |
| CVSS 3.1 | 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N Open in the calculator |
| CVSS 4.0 | 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1125: Excessive Attack Surface |
| OWASP Top 10 | A06:2025 Insecure Design |
| MITRE ATT&CK | T1190 Exploit Public-Facing Application, T1210 Exploitation of Remote Services |
| Category | Security Misconfiguration |
Description
Hosts and devices often run network services that are not needed for their role, because they are enabled by default in the operating system or product, were installed for a past purpose, or were left behind after testing. Examples include default web servers and administration consoles, sample applications, legacy services such as echo, chargen, discard and finger, file sharing on systems that share no files, and remote access or monitoring agents that are no longer used.
Each listening service is code that an attacker can reach and test. An unnecessary service does not in itself give an attacker access, but it adds to the number of ways in, and services that nobody uses are also the least likely to be patched, monitored or configured securely, so they tend to accumulate known vulnerabilities and default settings over time. A vulnerability, a default credential or a weak configuration in such a service can provide an initial foothold, a route to sensitive information or a means of disrupting the host, and the service's presence discloses information about the host's role and software. The risk rises when the services are reachable from the internet or from large user networks, and falls when they are filtered so that only administrative systems can connect.
The weakness is identified by a port scan of each host, for example with Nmap, compared with the services that the host's role requires. The system owners usually need to confirm which services are unneeded, so the finding is often raised as a list of services for review. Where a needed service is weakly configured, that weakness is reported separately.
Remediation
- For each service identified, confirm with the system owner whether it is required. Disable and uninstall services that are not, rather than only stopping them, so that they do not return after a restart or update.
- Restrict the services that remain with host and network firewalls so that they are reachable only from the systems and networks that need them, and bind them to specific interfaces rather than all interfaces where the software allows.
- Build systems from hardened baselines that start with the minimum services enabled, such as the CIS Benchmarks or vendor security baselines, and record the expected listening ports for each server role.
- Scan internal and external address ranges regularly and compare the results with the recorded baseline, so that new services are noticed and reviewed.
As an interim measure, block the services at the network firewall. Confirm the fix by repeating the port scan and checking that only the expected services respond.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.