> 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-url-snapshot-pentesting-web.md).

# IDOR URL スナップショット

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

**初期観察** を解析した後 **pcap** ファイルをWiresharkで解析すると、直接悪用可能な内容は見つかりません。

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

しかし、ファイルをアップロードするたびに、 **スナップショット** が作成されることがわかります。URLの対応部分にはスナップショットの識別子を指定するパラメータが含まれており、たとえば次のようになります。 `snapshot_data=2`.

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

URLのパラメータを変更してスナップショット0にアクセスすると、機密情報を含むファイルが取得できます。

### **Wiresharkによる解析**

ファイルのフレームを調べると **pcap**、ユーザーの認証情報を特定できます。

* ユーザー名: `nathan`
* パスワード: `Buck3tH4TF0RM3!`

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-b4320d63bef95cbbcd57fac04cb2412e101b40db%2Fimage%20(2645).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-vulnerabilities/insecure-direct-object-reference-idor-attack/idors-url-snapshot-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.
