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

Feature request: Ingest NMAP XML file as targets #782

Open
d-woosley opened this issue May 9, 2024 · 2 comments
Open

Feature request: Ingest NMAP XML file as targets #782

d-woosley opened this issue May 9, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@d-woosley
Copy link

Thank you so much for this great tool! I use it at least once a week on pentests.

As part of my internal pentest workflow, I will perform directory enumeration against the whole internal network. However, to do this right now I have to run a tool to figure out which ports support HTTP(S) and then parse that tool output and send it as input to ffuf. It would be very helpful to have an option that would ingest a straight Nmap XML file, attempt HTTP and HTTPS connections to each port to see what port/host combo's support HTTP(S), and then kickoff a directory enumeration scan with ffuf.

Something like the following:

ffuf -w portscan.xml:NMAP -w wordlist.txt:PATH -u NAMP/PATH
@bsysop
Copy link
Collaborator

bsysop commented May 17, 2024

Hi @d-woosley, this is very specific, you could use a bash/python wrapper!

@bsysop bsysop added the enhancement New feature or request label May 17, 2024
@joohoi
Copy link
Member

joohoi commented May 20, 2024

Yeah, doing this outside of ffuf is preferred. The general design philosophy is "if you can do it outside of ffuf, you should".

This is in place in order to not to bloat the codebase into a unmaintainable behemoth, trying to support every and all use cases, I hope you understand :)

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

No branches or pull requests

3 participants