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

TODO nmap input file clarification #216

Open
petrock6 opened this issue May 20, 2017 · 2 comments
Open

TODO nmap input file clarification #216

petrock6 opened this issue May 20, 2017 · 2 comments

Comments

@petrock6
Copy link

The TODO file says -oM files should be supported from nmap. The current version of nmap doesn't have a -oM output flag. If I started to work on this, would XML be acceptable?

If I understand correctly, the goal is to import nmap output files into hydra so that any hosts with a specific service running will be added to a bruteforcing queue. A potential problem will be when some services are running on nonstandard ports, which may result in bruteforcing on incorrect services. Perhaps it can just force the user to specify a port option?

@vanhauser-thc
Copy link
Owner

it is more difficult than that :)
e.g. it would not make sense to attack ftp, telnet and ssh if they are all there, but e.g. snmp and oracle would.
also - they would require different login/password lists.

So I am not sure this feature would make sense.

I put it in as a maybe thing if it would make sense. So far I did not find a way which would make it obvious for users how it works and that it is a useful feature too.

@petrock6
Copy link
Author

petrock6 commented May 20, 2017

Perhaps there can be an argument like -nmap "nmap args" -- so hydra will actually call nmap. Additionally, hydra can force that users specify a list of services in nmap (or at least a list of port numbers.)

As per the different login/password lists, I can't think of any solution that is user friendly. Maybe tell users something like:

hydra -L users -P passes -nmap "-p21,22,25 192.168.1.*"

Where users isn't users.txt, but instead:
users.ftp.txt
users.ssh.txt
users.smtp.txt

And passes isn't passes.txt, but instead:
passes.ftp.txt
passes.ssh.txt
passes.smtp.txt

Or for the lazy users who want to use only one user and one pass file, add an option like "--nmap-force-single-user-file" or "--nmap-force-single-password-file."

A bit hackish, but someone who reads the man should be able to figure it out.

As per actually getting multiple services cracking at once... it's gonna need a LOT of code rewriting.

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

No branches or pull requests

2 participants