diff options
author | bitform <matt@exploit-monday.com> | 2012-09-11 19:01:02 -0400 |
---|---|---|
committer | bitform <matt@exploit-monday.com> | 2012-09-11 19:01:02 -0400 |
commit | 688ba7911c38b985990011c93a5f1d40232e39e7 (patch) | |
tree | 8ba4d2c1b27cf3c27e7dd25fde3e2031e33833fb /Inject-Dll.ps1 | |
parent | 0280779d011e965a8b2e7d3c8f659ccdf811d2e5 (diff) | |
download | PowerSploit-688ba7911c38b985990011c93a5f1d40232e39e7.tar.gz PowerSploit-688ba7911c38b985990011c93a5f1d40232e39e7.zip |
Improved Metasploit payload support for 32/64-bit
Updated Inject-Shellcode. If running a 32-bit Metasploit payload from
64-bit PowerShell, it will prompt the user to execute the payload from
32-bit PowerShell. This fix was in response to Chris Gate's feature
request:
http://carnal0wnage.attackresearch.com/2012/05/powershell-shellcode-metasploit-x64.html
Note, there are some side effects:
1) It takes about one minute to initialize and execute the payload in
the 32-bit process. This is because the execution essentially emulates
copying and pasting its contents into the child process.
2) You will see some output artifacts of the script running in the child
PowerShell process.
I couldn't think of a good way to rectify these problems without
dropping the contents of the script to disk, which would not be
desireable.
Diffstat (limited to 'Inject-Dll.ps1')
0 files changed, 0 insertions, 0 deletions