You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently fuzzing in nuclei is designed / logically seperated into key-value fields.
fuzzing:
- part: querytype: replacemode: multiplevalues:
- "^[0-9]+$"# only if value is numberfuzz:
- '{{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: headerstype: replacemode: singlefuzz:
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)
The text was updated successfully, but these errors were encountered:
Proposed Changes
Currently fuzzing in nuclei is designed / logically seperated into key-value fields.
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
The text was updated successfully, but these errors were encountered: