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

# Creating a vulnerable environment with VulnAD

Active Directory security notes for Creating a vulnerable environment with VulnAD, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps

In this lab, we use a script to intentionally create vulnerable users, groups and permissions in Active Directory.

The objective is to be able to practice:

* identify weak ACLs;
* understand privilege paths;
* exploit poorly configured permissions;
* visualize relationships in BloodHound.

Load the script:

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

{% code overflow="wrap" %}

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

{% endcode %}

Then we execute:

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

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

This command creates several objects in the domain:

* users;
* groups;
* permission relationships;
* Vulnerable ACLs;
* exploitable privilege paths.

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