> 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/ssrf/blind-ssrf-with-out-of-band-detection.md).

# Out-of-Band検出を伴うブラインドSSRF

PortSwigger Web Security Academy のラボ向けメモ。Out-of-Band検出を伴うブラインドSSRFに関するもので、攻撃手順、ペイロードのテスト、Burp Suite による検証、および対策の文脈を含む。

### アウト・オブ・バンド検知を伴うブラインドSSRF

このラボでは、URLに対してHTTPリクエストを実行する分析モジュールを使用します。 **リファラー** ヘッダーが、製品ページの読み込み時に使用されます。/ ラボを解くには、この動作を利用して公開サーバーへのリクエストを発生させる必要があります。 **Burp Collaborator**.

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

ページが Referer ヘッダーの値を取得していることがわかります。/ したがって、目的はこのリクエストを私たちの Collaborator のボディへリダイレクトすることです。

悪意のある Refererer を含むクエリを送るだけです。例えば:

```
Referer: https://ld2xyh6ornbpdovp5ww0sartzk5bt1hq.oastify.com
```

その後、サーバーが外向きのクエリを実行し、それが Burp Collaborator に表示されることで、ブラインドSSRFの動作が確認できます。

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-0db3bc364786d27138b9b40fb14a31df6cca91e5%2Fimage%20(345).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/ssrf/blind-ssrf-with-out-of-band-detection.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.
