feat: Add random path probing to bypass Next.js middleware redirects #28
+5
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Team,
This PR addresses False Negatives caused by
middleware.tsredirects on the root path (/).The Problem:
Currently, the scanner defaults to probing
["/"]. In many Next.js deployments, the root path redirects (e.g.,307to/login). This redirection often strips the POST body before the RSC parser processes it, causing the scanner to miss vulnerable targets.The Fix:
I updated the default logic to probe both
/AND/{random_string}.Hitting a non-existent path triggers the Next.js Global Not Found handler (which is an RSC). This forces the server to parse the payload regardless of authentication middleware or root redirects.
Issue associated: Fixes #27
Cheers!