Skip to content
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

All encoders failed to encode #14130

Closed
plusplus99 opened this issue Sep 13, 2020 · 4 comments
Closed

All encoders failed to encode #14130

plusplus99 opened this issue Sep 13, 2020 · 4 comments
Assignees
Labels
bug confirmed Issues confirmed by a committer

Comments

@plusplus99
Copy link

I am trying to use this exploit on HTB : https://www.rapid7.com/db/modules/exploit/windows/smb/ms08_067_netapi

pretty simple yet metasploit gives me an error : all encoders failed to encode

I have spent hours trying to find a solution but I found nothing :/

This is screenshot for the error https://ibb.co/sQ5cCFY

Metasploit version is 6.0.2-dev

I am really frustrated and I am about to give up on my first box.

@plusplus99 plusplus99 added the question Questions about Metasploit Usage label Sep 13, 2020
@franferrax
Copy link

Hi, sorry for the duplicate. I've just reported the same issue in #14141. I provided further information to help solving this issue (including the 6f15368 commit spotted by git bisect) but I'm afraid I don't have a fix or workaround for it.

@IdanSaadon
Copy link

Hey!
I had the same issue. After a lot of attempts I got the solution - just change the payload.
you can use show payloads to see all payloads. I chose the payload windows/meterpreter/reverse_tcp_allports cause it's very similar to the original (by name, the original is windows/meterpreter/reverse_tcp).
command:

msf6 exploit(windows/smb/ms08_067_netapi) > set payload windows/meterpreter/reverse_tcp_allports

Good Luck! :)

@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale Marks an issue as stale, to be closed if no action is taken label Oct 28, 2020
@smcintyre-r7 smcintyre-r7 self-assigned this Oct 30, 2020
@smcintyre-r7 smcintyre-r7 added bug confirmed Issues confirmed by a committer and removed Stale Marks an issue as stale, to be closed if no action is taken question Questions about Metasploit Usage labels Oct 30, 2020
@smcintyre-r7
Copy link
Contributor

This was fixed when #14177 landed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug confirmed Issues confirmed by a committer
Projects
None yet
Development

No branches or pull requests

4 participants