Kerberos Key-List-Request and Replies #147
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implemented code to complete the Kerberos Key List attack. This attack is completed by forging RODC (or AzureADSync RODC) TGTs and then requesting the long term key from a writable domain controller.
Example usage:
Step 1 - Create TGT
Generate Golden Ticket using KRBTGT_11442 account (rodcNumber + aes256 hash) to get the partial TGT for UserAllow with rid of 4234 in domain.local
Step 2 - Create and send TGS request to DC
Now we have our forged TGT (ticket.kirbi), we use asktgs to send a keyList request to a writable domain controller for krbtgt service.
Screenshots
References: