fix(fuzz): use effective parameter for frequency tracking#7050
fix(fuzz): use effective parameter for frequency tracking#7050Rhan2020 wants to merge 1 commit intoprojectdiscovery:devfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Organization UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
WalkthroughA parameter reference in the fuzz parameter frequency check was replaced from Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Neo - PR Security ReviewNo security issues found Highlights
Comment |
Fixes a bug in fuzz param frequency tracking where we computed an
actualParameter(e.g. numeric path segment -> real segment value) but still fed the originalparameterinto the frequency tracker.This could cause unrelated inputs to collide under numeric indices and suppress legitimate fuzzing.
Changes:
actualParameterwhen callingFuzzParamsFrequency.IsParameterFrequent.Proof:
go test ./.../claim #6398
Summary by CodeRabbit