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

Add Option to Follow Redirection #50

Open
tzuk-pl opened this issue May 29, 2019 · 4 comments
Open

Add Option to Follow Redirection #50

tzuk-pl opened this issue May 29, 2019 · 4 comments

Comments

@tzuk-pl
Copy link

tzuk-pl commented May 29, 2019

Pretty simple and straight forward feature request:

Add the ability to follow redirections within auto repeater. I'm thinking it would be useful to have a button similar to how repeater has a button to follow redirections for individual requests/responses, and have a checkbox to automatically follow redirection in the options section.

Find below two crude mockups of what I mean in case it isn't quite clear.

Per Request:

image

Options:

image

Current workaround: just send your modified request(s) to repeater and use the "Follow Redirection" button in repeater.

Cheers!

@justinmoore
Copy link
Collaborator

justinmoore commented May 31, 2019 via email

@tzuk-pl
Copy link
Author

tzuk-pl commented May 31, 2019

Thanks for the response, Justin. Some of the applications I have tested use custom application gateways or custom behaviour that create a one-time use token and redirect to an endpoint on a different domain, but still part of the same application.

A simple example: A GET or POST request to http:https://applicationname/index is sent by the application which uses a cookie or a bearer token for authentication and a custom header like "X-CUSTOM-URI: /API/addmember" is sent in the request. The application responds with a redirection to a different domain such as http:https://apiname/api/addmember and provides some sort of one-time use or short-lived token to use in the request to the apiname site.

In this example, I would be browsing the application as a high privileged user and using autorepeater to repeat the requests to http:https://applicationname as a low privileged user who should not have the ability to add a new member. If the application provides a token and redirection to the API, and the add member request succeeds, it would indicate insecure permissions. The call to the API would have no portion to autorepeat, as the token and redirection was granted for the low privileged user by the http:https://applicationname site.

I installed autorepeater from the BAppStore a while back; I'll be sure to update, thanks for the recommendation.

@Nexsus1985
Copy link

Hi,

I agree with tzuk-pl.
I'm using this great extension mostly for auto fuzzing and checking the response for specific answers.
This option can help a lot because the redirecting force me to do more manual steps for analyzing the response, In some cases I have hundred of redirection responses so it become useless for those scenarios.
Hope that you will consider to add this option, I'm sure that it will help a lot to many researchers.

Thanks a lot.

@justinmoore
Copy link
Collaborator

justinmoore commented Aug 31, 2019 via email

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

No branches or pull requests

3 participants