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 [Add more clarity to the result and remove duplicates] #4908

Closed
reewardius opened this issue Mar 17, 2024 · 1 comment · Fixed by #5126
Closed

Feature request [Add more clarity to the result and remove duplicates] #4908

reewardius opened this issue Mar 17, 2024 · 1 comment · Fixed by #5126
Labels
Type: Enhancement Most issues will probably ask for additions or changes.
Milestone

Comments

@reewardius
Copy link

reewardius commented Mar 17, 2024

Please describe your feature request:

I propose to implement (if it already exists, provide a link to documentation and examples) the following functionality in recently extended fuzzing:

  1. display the vulnerable parameter, path, header, where the vulnerability was found, and HTTP method that was used to find the vulnerability, because when testing API the path can be the same, but HTTP methods are different, I would like to see the method and parameter where the problem is.
    image
    image

  2. Add flag -dedupe that will allow duplicate queries with the same parameters but different values to be removed, and then this can be used in fuzzing. How it is implemented in this toolkit:

https://github.com/ameenmaali/urldedupe
https://github.com/s0md3v/uro

image

Thank you!

@reewardius reewardius added the Type: Enhancement Most issues will probably ask for additions or changes. label Mar 17, 2024
@GeorginaReeder
Copy link

Thanks so much for this feature request @reewardius , we appreciate it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants