> 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-vulnerabilities/insecure-direct-object-reference-idor-attack/idors-techniques-pentesting-web.md).

# IDOR 手法

IDOR 手法に関する、Webアプリケーションのペネトレーションテスト、エクスプロイトのワークフロー、ペイロード検証、影響評価、修正の文脈でのメモ。

> IDOR脆弱性を悪用するには、攻撃者は **オブジェクトの識別子を変更する** URL内で、または自動化ツールを使って異なる値をテストします。攻撃者が、利用できるべきではないリソースへのアクセスを許可する識別子を見つけた場合、IDOR脆弱性の悪用は成功です。

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-20f398c75cc903c065c88fa74917c7a2c287baa1%2FPasted%20image%2020231107232257.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-402a16e4a356708a9c081a1d4c8da7cef85e0e33%2FPasted%20image%2020231107232328.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

## IDOR：

* 私たちはファイルを作成し、それを **識別子を返します** 番号1062として：

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-7b11c49201a22b11dc50f0e87413be47bca82611%2FPasted%20image%2020231107233252.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-c75d57c1d4ec6f3288f17093924a3e66e51133e4%2FPasted%20image%2020231107233334.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

別の番号で絞り込むと、その文書は **存在しません**:

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-11282d2e27250afe930ac8bcb7ec1dfb41661726%2FPasted%20image%2020231107233424.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

### ブルートフォース：

* 私たちは攻撃を仕掛けます **ブルートフォース** 存在するファイルを絞り込むには：

```bash
wfuzz --hh=10703,1233 -c -t 200 -z range,1-1500 -d 'pdf_id=FUZZ' http://localhost:5000/download

```

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-bf8c537bc6e72a0f90c5091c2aaee3fd3b904aa5%2FPasted%20image%2020231107234914.png?alt=media" alt="" width="563"><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-vulnerabilities/insecure-direct-object-reference-idor-attack/idors-techniques-pentesting-web.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.
