bcoles
commented
5 months ago As workaround, you can set PASSWORD anything. Metasploit will still use the USERPASS_FILE file.
Open alyaparan opened 5 months ago
bcoles
commented
5 months ago As workaround, you can set PASSWORD anything. Metasploit will still use the USERPASS_FILE file.
msf6 > use auxiliary/scanner/winrm/winrm_login msf6 auxiliary(scanner/winrm/winrm_login) > set RHOSTS [IP] RHOSTS => [IP] msf6 auxiliary(scanner/winrm/winrm_login) > set REMOVE_USERPASS_FILE true REMOVE_USERPASS_FILE => true msf6 auxiliary(scanner/winrm/winrm_login) > set USER_AS_PASS false USER_AS_PASS => false msf6 auxiliary(scanner/winrm/winrm_login) > set BLANK_PASSWORDS false BLANK_PASSWORDS => false msf6 auxiliary(scanner/winrm/winrm_login) > set USERPASS_FILE /usr/share/armitage/userpass4440.txt USERPASS_FILE => /usr/share/armitage/userpass4440.txt msf6 auxiliary(scanner/winrm/winrm_login) > set RPORT 5985 RPORT => 5985 msf6 auxiliary(scanner/winrm/winrm_login) > set DB_ALL_CREDS false DB_ALL_CREDS => false msf6 auxiliary(scanner/winrm/winrm_login) > run -j [*] Auxiliary module running as background job 57. [-] Auxiliary aborted due to failure: bad-config: The PASSWORD option is required unless using Kerberos authentication.