-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SAM Dump for accounts without secrets #1839
Comments
Hi @Dfte, |
I have tested this against a domain controller. Now it's ovbious that there are no hashes for such accounts in the SAM database which is disabled anyway for domain controllers. But is there really a reason to display an error for such use cases considering there is no way for a local account not to have at least a default LM/NT hash ? |
Hey, mm I don't think so. Will be playing with it a bit more and can create a PR to change it |
I realised that some defaults Windows accounts, like for example WDAGUtilityAccount, throw the following error:
However there is no error here. WDAGUtilisatyAccount does not have a NT hash in the SAM database because this is a virtual account used to contain applications in a sandbox (for example browsers) and these featuers are not used on windows servers. Considering I never saw secretsdump failing in dumping SAM database, I believe it is possible to switch the following liens from impacket/impacket/examples/secretsdump.py:
to
That way most of tools using impacket secretsdump won't have a messed up output.
Let me know what you think about this :)
The text was updated successfully, but these errors were encountered: