Process and propagate KERB-SUPERSEDED-BY-USER error details #20264
+121
−20
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.
While starting to look into the BadSuccessor attack it became apparent that Metasploit could benefit from processing the KERB-SUPERSEDED-BY-USER structure included in Kerberos error messages. This would be the case after an account has completed the migration process. FWIW, the error details also appear to be included even if the password is invalid so an attacker can identify an account has been migrated without knowing it's password.
Related to but does not complete #20217
Verification
msflab.local
/DC=msflab,DC=local
to the desired domainauxiliary/admin/kerberos/get_ticket
modulesvc_sql
account and use theGET_TGT
actionDemo