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.
This PR adds the ability to add specific flags to the TGS request so that the default (
forwardable, renewable, renewable_ok, canonicalize
) will not be finger printable by using the Impacket tool. During a recent Purple Team engagement, we were able to identify that Impacket does not follow the current Windows convention for ticket options on TGS requests. By allowing this PR, operators are able to adjust their TGS options to blend in with regular occurring TGS requests.This also reflects the options available in the Rubeus tool, specifically the
/flags
option.An example of the default impacket ticket:
An example of using only the
renewable
option:An example of using the new KRBTGSFLAGS environmental variable for setting specific flags:
Another example for multiple options would be:
Exporting this environmental variable should work for any current impacket tool (
wmiexec.py
,smbclient.py
,smbexec.py
,dcomexec.py
,psexec.py
, etc.). We have not tested all scenarios.Additionally, it may be advisable to change the default ticket options to only have
renewable
, so that the default options will not be the finger print of the Impacket tool.