You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm on my first run with all plugins enabled to see what happens. I notice a potential enhancement already, which would improve the efficiency of OWTF.
When the SNMP scanner is run, specifically "/opt/metasploit/apps/pro/msf3/msfcli auxiliary/scanner/snmp/snmp_enumusers", if the connection is refused it would then seem unnecessary to then also run the Metasploit login bruteforce "/opt/metasploit/apps/pro/msf3/msfcli auxiliary/scanner/snmp/snmp_login".
There is a substantial time sink in trying to then bruteforce a service that is not actually running.
What may be a better way would be to nmap the target (or other port discovery) and then apply only the related plugins, even if all are selected - with an option to run the dynamically disabled ones anyways.
This would provide faster reconnaissance overall, but still allow the tester to be thorough if they wish. I do note plugins can be manually skipped in the Worker page, being a little more intelligent about which enabled plugins to run would be rather nice.
Many thanks,
James
The text was updated successfully, but these errors were encountered:
Hello,
First off, great job on all of this!
I'm on my first run with all plugins enabled to see what happens. I notice a potential enhancement already, which would improve the efficiency of OWTF.
When the SNMP scanner is run, specifically "/opt/metasploit/apps/pro/msf3/msfcli auxiliary/scanner/snmp/snmp_enumusers", if the connection is refused it would then seem unnecessary to then also run the Metasploit login bruteforce "/opt/metasploit/apps/pro/msf3/msfcli auxiliary/scanner/snmp/snmp_login".
There is a substantial time sink in trying to then bruteforce a service that is not actually running.
What may be a better way would be to nmap the target (or other port discovery) and then apply only the related plugins, even if all are selected - with an option to run the dynamically disabled ones anyways.
This would provide faster reconnaissance overall, but still allow the tester to be thorough if they wish. I do note plugins can be manually skipped in the Worker page, being a little more intelligent about which enabled plugins to run would be rather nice.
Many thanks,
James
The text was updated successfully, but these errors were encountered: