> 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/path-traversal/path-traversal-with-start-of-path-validation.md).

# 起始路径验证的路径遍历

起始路径验证的路径遍历，PortSwigger Web Security Academy 实验笔记，包括利用流程、载荷测试、Burp Suite 验证以及修复上下文。

### 文件路径遍历，路径起始部分的校验

应用程序通过查询参数传输整个文件路径，并且只检查该路径 **的开头** 是否与预期文件夹匹配。这种校验是不够的：在允许的前缀后追加内容后，就有可能访问任意文件。

#### **分析**

文件名参数直接包含一个绝对路径，例如：

```bash
/var/www/images
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-0ecb977074c246375d014d04cfb0b6980b01da53%2Fimage%20(254).png?alt=media" alt=""><figcaption></figcaption></figure>

如果尝试经典的穿越：

```bash
../../../../../etc/passwd
```

应用程序会阻止它。

但是如果我们提供 **预期路径**，后面跟着 `../` 用于逃逸的序列，校验就无法检测到越界：

由于路径起始部分与 `/var/www/images/`完全匹配，检查会通过，但最终解析实际上指向 `/etc/passwd`.

```bash
/var/www/images/../../../../../etc/passwd
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-0d1dc24319c0bcc94915926664e561591ad27409%2Fimage%20(255).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/path-traversal/path-traversal-with-start-of-path-validation.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.
