Like any service created with CreateService() , if the path to the executable contains spaces and is not enclosed in quotes, Windows will try to interpret each space-separated token as an executable. For example:
When an attacker sends a malicious request to the NSSM service, the nssm_validate_service function processes the request and fails to properly validate the input parameters. This leads to a buffer overflow, which can be exploited by an attacker to execute arbitrary code on the system. nssm-2.24 exploit
There are no documented exploits for NSSM version 2.24 itself. However, Like any service created with CreateService() , if
NSSM 2.24 exploit refers to a local privilege escalation vulnerability found in the Non-Sucking Service Manager (NSSM) version 2.24. This tool is commonly used on Windows systems to run applications as services. Vulnerability Overview The core issue in NSSM 2.24 is an Unquoted Service Path vulnerability combined with weak file permissions. There are no documented exploits for NSSM version 2