> 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/web-cache-deception/cheating-cache-via-origin-server-side-normalization.md).
# 通过源站服务器端规范化欺骗缓存
面向 PortSwigger Web Security Academy 实验室的通过源站服务器端规范化欺骗缓存笔记，包括利用流程、载荷测试、Burp Suite 验证和修复背景。
### 利用源服务器规范化实施 Web 缓存欺骗
#### 实验目标
从用户处获取 \*\*API 密钥\*\* **carlos** 通过滥用一个 **缓存** 由原始服务器对 URL 进行规范化所触发的行为 **原始服务器**.
#### 访问
* 可通过以下方式连接： **wiener:peter**
* 实验室提供了一个分隔符列表（delimiter list），但这里的攻击主要基于 `../` 以及编码。
### 1）观察
* 在 **`/resources`** 目录中，有一个活跃的 **缓存**.
* 因此，思路是传递一个敏感页面（**`/my-account`**）作为一个“可缓存”的资源，使用一个 **路径穿越** 这将会被 **规范化** 由原始服务器进行。
测试示例：
```bash
/resources/../my-account
```
### 2）利用
#### 思路
1. 强迫受害者加载一个以以下内容开头的 URL： **`/resources/`** （以触发缓存）。
2. 返回到 **`/my-account`** 通过 `../` （或其编码变体）。
3. 将答案以某个键存入缓存，然后检索隐藏页面。
{% code overflow="wrap" %}
```javascript
```
{% endcode %}
根据你的测试： **它不起作用** 在这种状态下
### 3）变通：对后端进行编码
你指出你需要 **对……进行 URL 编码** 分隔符，以使原始规范化正常工作。
所使用的 URL：
```bash
/resources/..%2fmy-account?jordan
```
最终载荷：
```javascript
```
结果：服务器 **将……解释为** 按预期对 URL 进行解释（规范化），从而继续进行缓存攻击
---
# 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/web-cache-deception/cheating-cache-via-origin-server-side-normalization.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.
.png?alt=media)
