Closed zeroSteiner closed 6 years ago
I've encountered a similar issue with Linux x64 Meterpreter.
Selecting Linux x64 Meterpreter payload and running the module will work the first time. Running the module a second time, without changing anything, will raise invalid opcode arguments "push"
.
Total guess but I wonder if one of the arguments to push end up as nil: e.g https://github.com/rapid7/metasploit-framework/blob/47a324815d57d11989d2bbf5d0704e3bb096f3cb/lib/msf/core/payload/linux/x64/reverse_tcp.rb#L108 I can dig deeper tomorrow (on mobile).
I ran into this a few days ago. Not necessarily with to_handler
, but I can confirm this error is coming up.
I had quick play with this and retry_count is indeed nil. If it's just this payload we could just duct tape fix it (set it to 0 if nil), but I'm not sure why it's not being set yet.
Anyone wanna git bisect
this? Seems like a regression from recent-ish payload work.
This is biting me right now while testing #9876.
I'll bisect (tired after walking all day on the beach :)
Yep definitely an issue since db2e3f2ddd2c7db9dcd8ba533427ee4aa1a03ee3 . I should have caught that 8 months ago. @bwatters-r7 / @jmartin-r7 could you make sure this is in the payload test matrix?
Thanks all.
Steps to reproduce
The
linux/x64/meterpreter/reverse_tcp
payload fails to start a handler when issued theto_handler
command. The exception it throws isinvalid opcode arguments
(see below). The output then (incorrectly) states that a job has been started.Reproduce with the following steps
use payload/linux/x64/meterpreter/reverse_tcp
set LHOST x.x.x.x
to_handler
Expected behavior
The
to_handler
command should start a handler for the specified payload.Current behavior
System stuff
Metasploit version
Commit 47a324815d57d11989d2bbf5d0704e3bb096f3cb.
I installed Metasploit with:
OS
Fedora 27 x64