This module exploits a logic flaw due to how the lpApplicationName parameter
is handled. When the lpApplicationName contains a space, the file name is
ambiguous. Take this file path as example: C:\program files\hello.exe;
The Windows API will try to interpret this as two possible paths:
C:\program.exe, and C:\program files\hello.exe, and then execute all of them.
To some software developers, this is an unexpected behavior, which becomes a
security problem if an attacker is able to place a malicious executable in one
of these unexpected paths, sometimes escalate privileges if run as SYSTEM.
Some software such as OpenVPN 2.1.1, OpenSSH Server 5, and others have the
The offensive technique is also described in Writing Secure Code (2nd Edition),
Chapter 23, in the section "Calling Processes Security" on page 676.
This technique was previously called Trusted Service Path, but is more commonly
known as Unquoted Service Path.
The service exploited won't start until the payload written to disk is removed.
Manual cleanup is required.
- sinn3r <email@example.com>