Application Allowlisting Not Enforced
No application control policy is enforced, so users and malware can run any program or script, including unapproved code saved in user-writable locations.
| Severity | Medium |
| CVSS 3.1 | 4.4 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N Open in the calculator |
| CVSS 4.0 | 4.8 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-829: Inclusion of Functionality from Untrusted Control Sphere |
| OWASP Top 10 | A08:2025 Software or Data Integrity Failures |
| MITRE ATT&CK | T1204.002 Malicious File, T1059 Command and Scripting Interpreter |
| Category | Security Misconfiguration |
Description
No application control policy restricts which programs, scripts and libraries can run, so users, and any malware acting as them, can run any executable, script or installer they can write to disk, including files saved in their profile, temporary folders, downloads or removable media. Malware delivered by phishing, malicious downloads or removable media runs without restriction, and an attacker with access to a user's session can run their own tools for discovery, credential theft and lateral movement. The weakness gives an attacker no access in itself, and code that runs is limited to the privileges of the user whose session runs it. Partial deployments are also common: a policy left in audit mode, rules that cover executables but not scripts, installers or DLLs, broad path rules that allow user-writable folders, or no protection against signed Windows binaries that can be misused to run other code.
Application allowlisting, delivered on Windows by App Control for Business (formerly Windows Defender Application Control) or AppLocker, and on Linux by tools such as fapolicyd or by mounting writable file systems with noexec, allows only approved software to run. It is one of the most effective defences against commodity malware and ransomware, so without it the host relies on detection by endpoint protection alone.
Its absence is identified by reviewing the effective policy, for example with Get-AppLockerPolicy -Effective or by checking for an active App Control policy, and by running a harmless unapproved executable and script as a standard user from a user-writable directory.
Remediation
- Deploy application control in audit mode first to build an inventory of the software in use, then enforce it. On Windows, App Control for Business is the stronger option; AppLocker can be used where it is already established.
- Base rules on publisher signatures or file hashes rather than paths, and never allow execution from user-writable locations such as user profiles,
%TEMP%, download folders and removable media. - Cover scripts (PowerShell, VBScript, JScript and HTML applications), Windows Installer packages and, where practical, DLLs, as well as executables.
- Apply Microsoft's recommended block rules for signed Windows binaries that can be misused to run arbitrary code, and keep them current.
- On Linux servers, use fapolicyd or an equivalent, and mount
/tmp,/var/tmp,/dev/shmand home directories withnoexecwhere workloads allow.
Manage policies centrally through Group Policy, Intune or configuration management, and review audit events before each tightening. As an interim measure, enforce rules that block execution from user-writable paths, which stops much commodity malware with little disruption. Confirm enforcement by repeating the test with an unapproved executable and script.
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.