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

Support KV Fuzzing in Fuzz rules #4848

Closed
Tracked by #4795
tarunKoyalwar opened this issue Mar 7, 2024 · 0 comments · Fixed by #4477
Closed
Tracked by #4795

Support KV Fuzzing in Fuzz rules #4848

tarunKoyalwar opened this issue Mar 7, 2024 · 0 comments · Fixed by #4477
Assignees

Comments

@tarunKoyalwar
Copy link
Member

tarunKoyalwar commented Mar 7, 2024

Proposed Changes

Currently fuzzing in nuclei is designed / logically seperated into key-value fields.

    fuzzing:
      - part: query
        type: replace
        mode: multiple
        values: 
          - "^[0-9]+$" # only if value is number
        fuzz:
          - '{{nums}}'

so fuzzing rule in above format will only fuzz every value of query params (map), and key cannot be fuzzed nor it was possible to pass both key and value ( ex: new query param pair altogether ) at once , but with kv this should be possible

In below fuzzing rule we are adding new headers altogether by specifying / passing kv combination in fuzz section

    fuzzing:
      - part: headers
        type: replace
        mode: single
        fuzz:
          X-Forwarded-For: "{{domain}}"
          X-Forwarded-Host: "{{domain}}"
          Forwarded: "{{domain}}"
          X-Real-IP: "{{domain}}"
          X-Original-URL: "{{domain}}"
          X-Rewrite-URL: "{{domain}}"
          Host: "{{domain}}"
          # " Host": "{{domain}}" # space before host (not supported yet due to lack of unsafe mode)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant