Open andrewhenke opened 4 years ago
I did just run git pull
and pull an update, however I ran the module again, and it still hasn't changed the performance from the situation described in my original message. I didn't think it would, as the changes were to README.md
and two of the wordlists. Just wanted to let you know.
The Routersploit Version is still Version: 3.4.1
I believe that this may have something to do with a device)target showing as positive (vulnerable) to an exploit, but not using the architecture the exploit is intended for. I experienced the same issue as my original issue with a device I knew wasn't the mipsle or mipsbe architecture and it did the same error. However, I was also able to achieve the same error on a different exploit module as well. I'll provide more information and specifics if it would be helpful, just let me know!
Same problem here.
Steps to Reproduce (for bugs)
Taking it from the initial startup of the program to error, here are the steps I've taken.
sudo python3 rsf.py
use scanners/autopwn
set target 54.77.xx.xxx
(IP Address redacted for client confidentiality, if it is desired to be disclosed please contact me directly)run
Upon completion of the scan, the target is vulnerable to:
use exploits/routers/linksys/eseries_themoon_rce
set target 54.77.xx.xxx
run
Output:[+] Welcome to cmd. Commands are sent to the target via the execute method. [*] For further exploitation use 'show payloads' and 'set payload' commands.
And then I have to restart the program, reload global configuration/port settings, etc, and then, if I was to attempt to just run steps 5 and forward (in the above replication steps), it would, and will, still give the same errors with the same result as detailed above.
Your Environment
Linux kali 4.19.118-Re4son-v7+ armv7l GNU/Linux
Python 3.8.3
Current Behavior
Currently, and for several weeks, the eseries_themoon_rce module has been throwing multiple errors resulting in the complete exit of the program upon execution of either payload contained within the module, on either architecture. I have avoided the use of the module as much as I can, in the spirit of a future update potentially correcting the error but it is immediately relevant to my current work project so I decided to make contact regarding the error.
Expected Behavior
I expected that the module would, at the least, function correctly instead of error-exiting, although I have experienced on-and-off issues of various natures with this particular module for quite a few years now.