[tgssub.py] New example script: adding tgssub for SPN-jacking and manual sname manipulation#1256
[tgssub.py] New example script: adding tgssub for SPN-jacking and manual sname manipulation#1256ShutdownRepo wants to merge 5 commits into
Conversation
Can you give more details (debug print, screenshot) of what you're trying to do? |
If you're referring to https://github.com/SecureAuthCorp/impacket/pull/1256/files#diff-6282295c24020ba24be7e2a8a1133327088ab06cd43bded706a193ec283ea1e7R49, as you can see this line is in an "if/else" statement checking the presence of "/" in the original ticket's sname. Have you even tried before pointing this out? |
…t/cccache credentials Co-authored-by: wqreytuk <wochinijiamile@qq.com>
|
Worked with @wqreytuk, this feature needs further testing, but it now works on our end. The substitution wasn't complete. The information in the ticket wasn't replaced. Only the information in the credential object was. This is now fixed. |
fortra#1256 new tgssub example script

Example script to allow for SPN-jacking and manual manipulation of tickets to edit the sname (i.e. SPN) the ticket is issued for.
Python equivalent to
Rubeus tgssubcommand (https://github.com/GhostPack/Rubeus#tgssub)This can be done because the service name is not in the encrypted part of the ticket (cf. Wagging the Dog).
This is already done in Impacket internals with the AnySPN technique but now, attackers can use this standalone script, along with
describeTicket.pyfrom #1201 to manipulate (Rubeus tgssub) and inspect tickets (Rubeus describe) manually.References