If you must use NSSM, migrate to version 2.24 . Better yet, use a maintained alternative like WinSW with XML configuration files that support integrity checks. Conclusion NSSM 2.24 privilege escalation is not a classic buffer overflow or race condition—it is a design weakness amplified by common misconfigurations. Attackers love it because it turns a low-privilege foothold into full SYSTEM access with minimal noise.
But the real prize is . On many systems, authenticated users can enumerate and modify NSSM-managed services due to overly permissive service security descriptors. Technical Deep Dive: How the Escalation Works Step 1 – Enumeration An attacker with low-privileged access (e.g., a standard user on a compromised workstation or via a reverse shell) first enumerates all services:
sc qc <service_name> If the BINARY_PATH_NAME points to an NSSM executable (e.g., C:\nssm-2.24\win32\nssm.exe ), the service is a candidate. Using accesschk.exe from Sysinternals or PowerShell, the attacker checks if they have SERVICE_CHANGE_CONFIG or WRITE_DAC rights: nssm-2.24 privilege escalation
Stay secure. Never trust legacy wrappers with SYSTEM privileges.
net stop <service_name> net start <service_name> The service runs as (by default for manually installed services), executing malware.exe with the highest privileges. Step 5 – Persistence & Lateral Movement The malware can now add a new admin user, dump credentials from LSASS, or implant a backdoor—all while masquerading as a legitimate service. Real-World Attack Scenario Imagine a corporate environment using a legacy monitoring agent installed via NSSM 2.24 on hundreds of Windows Server 2012 R2 machines. A contractor with limited access discovers the NSSM service LegacyMonitor has its binary stored in C:\ProgramData\Monitor\ . The ProgramData folder, by default, grants BUILTIN\Users write access. If you must use NSSM, migrate to version 2
accesschk.exe -uwcqv "Authenticated Users" <service_name> accesschk.exe -uwcqv "BUILTIN\Users" <service_name> If the attacker has write access to the service configuration (often misconfigured in legacy systems), they can proceed. The attacker changes the binPath to point to a malicious executable they control:
sc config <service_name> binPath= "C:\temp\malware.exe" Or, if using NSSM directly: Attackers love it because it turns a low-privilege
sc query state= all | findstr "SERVICE_NAME" They then check for NSSM-managed services by looking for display names or descriptions containing "NSSM" or by inspecting the binary path:
Unlock fantastic savings at Soldier-Photos.com today with the latest coupons and promo codes that guarantee amazing discounts!
Last Updated: Mar 9th, 2026
If you must use NSSM, migrate to version 2.24 . Better yet, use a maintained alternative like WinSW with XML configuration files that support integrity checks. Conclusion NSSM 2.24 privilege escalation is not a classic buffer overflow or race condition—it is a design weakness amplified by common misconfigurations. Attackers love it because it turns a low-privilege foothold into full SYSTEM access with minimal noise.
But the real prize is . On many systems, authenticated users can enumerate and modify NSSM-managed services due to overly permissive service security descriptors. Technical Deep Dive: How the Escalation Works Step 1 – Enumeration An attacker with low-privileged access (e.g., a standard user on a compromised workstation or via a reverse shell) first enumerates all services:
sc qc <service_name> If the BINARY_PATH_NAME points to an NSSM executable (e.g., C:\nssm-2.24\win32\nssm.exe ), the service is a candidate. Using accesschk.exe from Sysinternals or PowerShell, the attacker checks if they have SERVICE_CHANGE_CONFIG or WRITE_DAC rights:
Stay secure. Never trust legacy wrappers with SYSTEM privileges.
net stop <service_name> net start <service_name> The service runs as (by default for manually installed services), executing malware.exe with the highest privileges. Step 5 – Persistence & Lateral Movement The malware can now add a new admin user, dump credentials from LSASS, or implant a backdoor—all while masquerading as a legitimate service. Real-World Attack Scenario Imagine a corporate environment using a legacy monitoring agent installed via NSSM 2.24 on hundreds of Windows Server 2012 R2 machines. A contractor with limited access discovers the NSSM service LegacyMonitor has its binary stored in C:\ProgramData\Monitor\ . The ProgramData folder, by default, grants BUILTIN\Users write access.
accesschk.exe -uwcqv "Authenticated Users" <service_name> accesschk.exe -uwcqv "BUILTIN\Users" <service_name> If the attacker has write access to the service configuration (often misconfigured in legacy systems), they can proceed. The attacker changes the binPath to point to a malicious executable they control:
sc config <service_name> binPath= "C:\temp\malware.exe" Or, if using NSSM directly:
sc query state= all | findstr "SERVICE_NAME" They then check for NSSM-managed services by looking for display names or descriptions containing "NSSM" or by inspecting the binary path: