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

Fuzzing templates seem to error out when url has the same parameter more than once. #4907

Closed
GKNSB opened this issue Mar 17, 2024 · 0 comments · Fixed by #4925
Closed

Fuzzing templates seem to error out when url has the same parameter more than once. #4907

GKNSB opened this issue Mar 17, 2024 · 0 comments · Fixed by #4925
Assignees
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@GKNSB
Copy link

GKNSB commented Mar 17, 2024

Nuclei version:

Current nuclei version: v3.2.2 (latest)

Current Behavior:

When a url that has multiple same parameters is passed to a fuzzing template, it seems to be failing to parse the variables.

Expected Behavior:

On versions prior to 3.2.x I wasn't having those errors.

Steps To Reproduce:

Example url:

https://example.com/test/view.action?ids=15139447&ids=15138969&ids=45842452&ids=15139259

Template used:

https://github.com/projectdiscovery/fuzzing-templates/blob/main/xss/reflected-xss.yaml

Command run:

nuclei -u "https://example.com/test/view.action?ids=15139447&ids=15138969&ids=45842452&ids=15139259" -t ~/fuzzing-templates/xss/reflected-xss.yaml -fuzz

Output similar to the following:
image

@GKNSB GKNSB added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Mar 17, 2024
@tarunKoyalwar tarunKoyalwar linked a pull request Mar 20, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants