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

The default view of opening fuzzer window, can not add locations #8492

Closed
1 task
wallenZhao2046 opened this issue May 17, 2024 · 3 comments
Closed
1 task

Comments

@wallenZhao2046
Copy link

Describe the bug

When open fuzzer window, the default view can not add locations, the add button in fuzzer location dialog is disabled. You have to click the combination to display Header and body button, then the add button in fuzzer location dialog will be enabled. For first-time users of Fuzzer, it can be confusing as to why the inability to set a location causes the Fuzzer to be unusable.

The default view, the add button is disabled
image

Clicked to display header and body button, the add button is enabled
image

Steps to reproduce the behavior

  1. From the site list, select the HTTP request you want to fuzz test. Right-click and select Attack ⇒ "Send to Fuzzer".
  2. In the fuzzer window, you will see this bug

Expected behavior

expect the add button in fuzzer location dialog is enabled. Or the default view is the combination to display Header and body.

Software versions

Zap version 2.15.0

Screenshots

No response

Errors from the zap.log file

No response

Additional context

No response

Would you like to help fix this issue?

  • Yes
@kingthorin
Copy link
Member

kingthorin commented May 17, 2024

I believe that's by design.

How would ZAP know where you want the payload added?

🤪 As far as I know we don't have any neural input options 🤪

If there's a bug it's actually that position 0 in the header is selected when changing views.

@thc202
Copy link
Member

thc202 commented May 17, 2024

That's not a bug either.

@thc202 thc202 removed the bug label May 17, 2024
@kingthorin
Copy link
Member

Please let us know if you feel something is outstanding here.

@kingthorin kingthorin closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants