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

SNMP Scanner and Remaining SNMP Plugins #4

Open
viyatb opened this issue Aug 15, 2017 · 0 comments
Open

SNMP Scanner and Remaining SNMP Plugins #4

viyatb opened this issue Aug 15, 2017 · 0 comments

Comments

@viyatb
Copy link
Member

viyatb commented Aug 15, 2017

thanks to @jamfwright

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant