The nssm (Non-Sucking Service Manager) is a service manager for Windows that allows users to manage and monitor system services. Version 224 of nssm has been identified as vulnerable to a privilege escalation attack. This report summarizes the findings and provides recommendations for mitigation.
The second finding involves NSSM’s Startup directory setting. By default, NSSM launches the service within the directory of the target executable. If the attacker can write to a parent directory, they can perform a DLL planting attack: nssm224 privilege escalation updated
If you found an NSSM service running as SYSTEM today, check its permissions immediately. Chances are, it’s a ticket to full compromise. Don’t let convenience ruin your security perimeter. NSSM 2
To test for or identify these vulnerabilities, security professionals use tools and manual commands: Chances are, it’s a ticket to full compromise
Since the original NSSM is largely unmaintained, consider migrating to actively supported alternatives like which prioritize secure default configurations. Service Hardening: Configure services to run under Managed Service Accounts (gMSA) or low-privilege accounts rather than LocalSystem whenever possible. certvde.com How to Proceed If you are managing a specific environment, I can help you: Write a PowerShell script to audit your system for insecure NSSM installations. Compare alternatives to NSSM for Windows Server 2025. Draft a security advisory for your internal IT team. CVE-2016-20033 Detail - NVD