> 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/fr/active-directory/lateral-movement/llmnr-nbt-ns-poisoning.md).
# Empoisonnement LLMNR / NBT-NS
Notes de sécurité Active Directory pour l'empoisonnement LLMNR / NBT-NS, couvrant l'énumération, Kerberos, les identifiants, l'abus des ACL, le mouvement latéral, le flux de travail d'exploitation et les étapes de validation.
Si l'accès se fait avec un nom valide, la résolution passe d'abord par le DNS du contrôleur de domaine.
{% code overflow="wrap" %}
```bash
dir //WS01/c$
```
{% endcode %}
Si le nom n'existe pas, Windows tente alors une résolution via `LLMNR` ou `NBT-NS` en broadcast.
{% code overflow="wrap" %}
```bash
dir //test/c$
```
{% endcode %}
Depuis Linux, nous pouvons écouter ces requêtes et y répondre avec `Responder`.
{% code overflow="wrap" %}
```bash
sudo responder -I ens33
```
{% endcode %}
Si une victime saisit le mauvais nom de partage, la requête atterrit alors sur notre machine.
{% code overflow="wrap" %}
```bash
dir //test/c$
```
{% endcode %}
Nous récupérons alors le hachage NTLM du compte tentant d'établir la connexion.
---
# 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/fr/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)