New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
persistence script vbs cannot run on x64? #6904
Comments
Can you try |
Ok, I just tested it, there is the same error, after I click "OK" on the pop window, it shows another warning from windows script Host, is there any succeed example command code? I am worrying if I did some misconfiguration. |
I couldn't reproduce this at my end. Target machine Windows 7, latest Metasploit git checkout:
|
@void-in Thank you very much for testing it out, unfortunately I still cannot spot any problem on my end. If it is possible, do you mind to send me a copy of your peresitence.rb under your exploit/windows/local/ database please? cause all other steps seem identical, I modified my persistence.rb for a few times, then switched back to the original version, but cant be too sure about that. Lot of Thanks |
I am using the one in the msf tree. You can examine it at https://github.com/rapid7/metasploit-framework/blob/05680ab6f30d6a8437ac1a8be6d9110764bbc725/modules/exploits/windows/local/persistence.rb |
Hello everyone,
With Kali, I just built an exe file with msfvenom, with payload windows/x64/meterpreter/reverse_tcp, and listen with multi/handler, the same payload, it all works fine, the target is a win7 x64 VPS.
The problem came when I tried to run persistence script, the target machine shows some VB warnings, briefly "the program is a 16 bit program, and the system is 64 bit, so it will stop, please contact the program supplier for a x64 edition", this the same massage appears when every time login too (I give the -X or -U flag).
I then tried this https://github.com/rapid7/metasploit-framework/blob/ee07809fd83f87d4cfc75525739820d1a87e2dfb/scripts/meterpreter/persistence.rb, result is the same.
I am not sure which part went wrong, please, any suggestion will be appreciated. Thank you!
The text was updated successfully, but these errors were encountered: