> 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/active-directory/acl-security-descriptors-and-permissions/vulnerable-environment-with-vulnad.md).

# 使用 VulnAD 创建易受攻击的环境

针对使用 VulnAD 创建易受攻击的环境的 Active Directory 安全笔记，涵盖枚举、Kerberos、凭据、ACL 滥用、横向移动、利用流程和验证步骤

在这个实验中，我们使用脚本在 Active Directory 中故意创建易受攻击的用户、组和权限。

目标是能够练习：

* 识别薄弱的 ACL；
* 理解权限路径；
* 利用配置不当的权限；
* 在 BloodHound 中可视化关系。

加载脚本：

{% embed url="<https://github.com/safebuffer/vulnerable-AD/blob/master/vulnad.ps1>" %}

{% code overflow="wrap" %}

```powershell
. ./vulnap.ps1
```

{% endcode %}

然后我们执行：

```powershell
Invoke-VulnAD -UsersLimit 100 -DomainName "whoami.local"
```

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

此命令会在域中创建多个对象：

* 用户；
* 组；
* 权限关系；
* 易受攻击的 ACL；
* 可被利用的权限路径。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-144104a816590b48b0b0b3376f32b9ab35f12e1b%2Fimage%20(3248).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/active-directory/acl-security-descriptors-and-permissions/vulnerable-environment-with-vulnad.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.