Error with Metasploit when generating staged implant #915
Answered
by
moloch--
An00bRektn
asked this question in
Q&A
-
|
Hi! I've been trying to use the staged payload functionality of the C2 for a while now, but I always run into some weird error. I ran the below commands: sliver > profiles new beacon --arch amd64 --os windows --mtls 10.10.69.24:443 -f shellcode --timeout 300 --seconds 5 --jitter 1 funnier_bytes
[*] Saved new implant profile (beacon) funnier_bytes
sliver > stage-listener --url https://10.10.69.24:8443 --profile funnier_bytes
[*] No builds found for profile funnier_bytes, generating a new one
[*] Job 3 (https) started
sliver > jobs
ID Name Protocol Port
==== ======= ========== ======
3 https tcp 8443
sliver > mtls --lhost 10.10.69.24 --lport 443
[*] Starting mTLS listener ...
sliver >
[*] Successfully started job #4
sliver > generate stager -r https --lhost 10.10.69.24 --lport 8443
[!] Error: rpc error: code = Unknown desc = exit status 2When I look at the logs, I see I installed Sliver on Kali 2022.2 using the bash one-liner in the README, and I can't really find any more info as to what's going on with Metasploit. I decided to ask here because I think it's more of a problem with my configuration as opposed to Sliver itself. |
Beta Was this translation helpful? Give feedback.
Answered by
moloch--
Sep 27, 2022
Replies: 1 comment 1 reply
-
|
The version of metasploit is too old, Sliver's stager supports MSF 6.2.17 or later |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
This worked, thank you! |
Beta Was this translation helpful? Give feedback.
Answer selected by
An00bRektn
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The version of metasploit is too old, Sliver's stager supports MSF 6.2.17 or later