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

# 带带外检测的盲 SSRF

带带外检测的盲 SSRF 笔记，适用于 PortSwigger Web Security Academy 实验室，包括利用流程、载荷测试、Burp Suite 验证和修复上下文。

### 带带外检测的盲 SSRF

该实验室使用一个分析模块，它会对以下 URL 发起 HTTP 请求： **Referer** 请求头，当产品页面加载时。/ 要解决该实验室，你必须利用这种行为触发对公共服务器的请求 **Burp Collaborator**.

<figure><img src="https://1574813340-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://1574813340-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/zh/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.
