PsExec/Winexec/ScExec
How do they work
The process is outlined in the steps below, illustrating how service binaries are manipulated to achieve remote execution on a target machine via SMB:
Copying of a service binary to the ADMIN$ share over SMB is performed.
Creation of a service on the remote machine is done by pointing to the binary.
The service is started remotely.
Upon exit, the service is stopped, and the binary is deleted.
Process of Manually Executing PsExec
Assuming there is an executable payload (created with msfvenom and obfuscated using Veil to evade antivirus detection), named 'met8888.exe', representing a meterpreter reverse_http payload, the following steps are taken:
Copying the binary: The executable is copied to the ADMIN$ share from a command prompt, though it may be placed anywhere on the filesystem to remain concealed.
Creating a service: Utilizing the Windows
sccommand, which allows for querying, creating, and deleting Windows services remotely, a service named "meterpreter" is created to point to the uploaded binary.Starting the service: The final step involves starting the service, which will likely result in a "time-out" error due to the binary not being a genuine service binary and failing to return the expected response code. This error is inconsequential as the primary goal is the binary's execution.
Observation of the Metasploit listener will reveal that the session has been initiated successfully.
Learn more about the sc command.
Find moe detailed steps in: https://blog.ropnop.com/using-credentials-to-own-windows-boxes-part-2-psexec-and-services/
You could also use the Windows Sysinternals binary PsExec.exe:
You could also use SharpLateral:
Last updated
