Handle kerberos properly when an account has no pre-auth required #18437
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 fixes an issue relating to accounts with Kerberos pre-auth disabled.
Upon encountering such an account, the KDC sends us an AS-REP that we could use for authentication, as long as we know the password. However, Metasploit has not performed this step. Rather, it just returns with "The account has pre-auth disabled; you can crack this ticket with Hashcat". This works fine for the kerberos brute force module; but for modules that actually intend to use kerberos to perform some action, the action will fail for such accounts. But if we know the account password, we can treat this exactly as with any other account: decrypt the AS-REP enc-part, and carry on.
This bug appeared when setting the correct password on a Kerberos module (e.g.
winrm_cmd
) would return with an error message, when it should be able to succeed:Verification
List the steps needed to make sure this thing works
msfconsole
use winrm_cmd
use kerberos_login