# Open Redirection Bypass

This bypass I found in a application while I doing pentesting. I hope it will helps you too!

1. While you I trying to redirect <https://targetweb.com?url=http://attackersite.com> it did not redirected!
2. I Created a new subdomain with with [www.targetweb.com.attackersite.com](http://www.targetweb.com.attackersite.com)
3. And when I tried to redirect with <https://targetweb.com?url=www.targetweb.com.attackersite.com>
4. It will successfully redirected to the [www.targetweb.com.attackersite.com](http://www.targetweb.com.attackersite.com) website!
5. Due to the bad regex it has been successfully bypass their protection!

## Authors:

* [@bishal0x01](https://twitter.com/bishal0x01)

## Reference Tweets:

* <https://twitter.com/bishal0x01/status/1262021038080053248>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://kathan19.gitbook.io/howtohunt/open-redirection/open_redirection_bypass.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
