Host Firewall Disabled

The host's built-in firewall is turned off for one or more network profiles, so every listening service is reachable from any network the host joins.

SeverityLow
CVSS 3.13.1 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N Open in the calculator
CVSS 4.02.3 CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-923: Improper Restriction of Communication Channel to Intended Endpoints
MITRE ATT&CKT1210 Exploitation of Remote Services, T1021 Remote Services
CategorySecurity Misconfiguration

Description

The host-based firewall, such as Windows Defender Firewall on Windows or nftables, iptables, firewalld or ufw on Linux, is disabled or set to allow all inbound connections, so every network service the host offers can be reached by anything that can route to it. On Windows the firewall has separate Domain, Private and Public profiles, and a common variant is one profile turned off, for example the Public profile used on untrusted networks, or the Domain profile disabled by Group Policy to simplify troubleshooting.

A host firewall complements network firewalls by restricting connections between hosts on the same network segment, which network devices often do not filter. Without it, services that should only be reachable from management systems, such as file sharing, remote management and RPC, are exposed to every system on the same network, including other compromised workstations, untrusted guest or public networks, and attackers who have gained a foothold. This widens the opportunity to exploit vulnerable or misconfigured services and to move laterally with stolen credentials. Exploitation still depends on a weakness in an exposed service, so the main effect is to increase the reach and speed of an attack.

The weakness is identified with Get-NetFirewallProfile or netsh advfirewall show allprofiles on Windows and the relevant firewall tool's status command on Linux, or by scanning the host from an adjacent system and finding services that a host firewall would normally block, such as SMB, RPC or remote management on workstations.

Remediation

  • Enable the host firewall for every profile and set the default inbound action to block. On Windows, enforce this through Group Policy (Computer Configuration\Policies\Windows Settings\Security Settings\Windows Defender Firewall with Advanced Security) or Intune, so that it cannot be turned off locally.
  • Allow inbound connections only for the services each role needs, and limit management protocols to the addresses of management systems and administrative workstations.
  • Where locally created rules are not needed, stop them from taking effect alongside central policy, using the profile setting that controls local rule merging.
  • On Linux, enable and persist the firewall service, for example with systemctl enable --now firewalld or ufw enable, with a default policy that denies inbound traffic.

As an interim measure, enable the firewall with rules that allow the services currently in use, and tighten the rules afterwards. Confirm the fix by checking each profile's status and repeating the scan from an adjacent host.

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 trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Windows and Linux Hosts Findings

Every Windows and Linux Hosts finding