Closed cdelafuente-r7 closed 10 months ago
Easiest way to fix this might be to check if you can add linux as a platform to the existing encoders where unix is already listed.
Hi!
This issue has been left open with no activity for a while now.
We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.
This issue came out while working on this PR. This comment gives more details.
When some
BadChars
are set, Framework tries to find a suitable encoder according to the platform and the architecture. With a fetch payload, it fails:When setting the payload to a standard command payload (e.g.
cmd/unix/reverse_bash
), it works.I found out the payload platforms are all set to
linux
platforms:So, no encoder is found with both a
cmd
architecture and alinux
platform:While with a command payload, the
unix
platform is correctly set:Steps to reproduce
linux/http/vinchin_backup_recovery_cmd_inject
)BadChars
are specified in the info hash (e.g.'Payload' => { 'BadChars' => "\"'<>&" }
)set payload cmd/linux/http/x64/meterpreter/reverse_tcp
exploit
Try again with a command payload
cmd/unix/reverse_bash
. It should work now.Expected behavior
The exploit should execute without encoding errors.
Current behavior
It fails with this error: